Windows APIs docs for older stuff from Win32 is extremely barebones. WinRT is better, but still can be confusing.
I think AI is really great to start with the systems programming, as you can tailor the responses to your level, ask to solve specific build issues and so on. You can also ask more obscure questions and it will at least point you at the right direction.
Apple docs are also not the best for learning, so I think as a documentation browser with auto-generating examples AI is great.
I have an M2 Macbook Air with 8GB and it struggles even without the light development part, and latest macOS made it all much worse. To be honest I am impressed how fast the experience degraded as there was a lot of headroom.
Apple seemed to copy this one exactly as iCloud asks you the same all the time. Honestly these days Linux feels like the only sane platform as you can customize it properly.
I am a big fan of the command line, but running linux as my daily driver is like trying to daily a kit car -- it breaks all the time and i spend more time than i want fixing it. With macos, i get my beloved command line, nice hardware, and a reliable OS. Win win win.
> I am a big fan of the command line, but running linux as my daily driver is like trying to daily a kit car -- it breaks all the time and i spend more time than i want fixing it.
Linux powers the entire world. Billions if not tens of billions of devices. It doesn't "break all the time like a kit car". I switched my wife's desktop from Ubuntu to Debian about a year ago and I haven't heard a single complain. Not a single crash. She hardly reboots her computer. The thing is just rock solid and it needs to be: she works from home and she spends 8 hours+ on her (Linux) computer.
Fair. Last time I tried to daily Linux was 2016 with a crappy dell I had laying around, and I am pretty sure that I did not know what I was doing. I have been on Mac since 2012 and I tried windows in 2019 only to regret it, then went back to mac.
That is also far from my experience. I'm starting to think it's more about you than about the tech. I have 5 machines running Linux, and they never break (1 server and 4 VMs). I have 4 machines running Windows (3 physical, 1 VM), with zero problems for many years.
The rise of Electron was purely because you can share the codebase for real with the web app (for lots of apps it is their main focus) and get cross-platform support for free.
Native apps are not bad to develop when using Swift or C#, they are nice to use and their UI frameworks are fine, it's just that it requires a separate team. With Electron you need much less, simple as that.
> As for the rest: minor variations in traffic light positioning and corner radii are topical but hardly indicators of decaying platorms.
I think it shows how important the platform itself is to the company. The system settings app on macOS is literally slow to change the topic (the detail page is updated like ~500ms after clicking).
I personally love to develop desktop apps but business-wise they rarely make sense these days.
I don't think it's worth to include the session -- it would bloat the context too much anyway.
However, I do think that a higher-level description of every notable feature should be documented, along with the general implementation details. I use this approach for my side projects and it works fairly well.
The biggest question whether it will scale, I suspect that no, and I also suspect it is probably better to include nothing than a poor/disjointed/rare documentation of the sessions.
I think a lot of companies are going to get burnt on these things. Sure it is easy to one-shot something which looks close, but then you are responsible for releasing/maintaining/improving.
Not to mention that you'd need to integrate it with lots of other vibe-coded products. It can be great for some use cases for sure, though, but identifying them can be tricky, as big orgs are pretty terrible at formulating what they need clearly.
You can't buy client performance, so it is just more visible. It's not like there are a lot of people with Rust/C++ back ends outside of some very critical pieces.
Also curious about this.
reply