4 ms·
There’s a real problem here: those are still the books to read if you really want to understand Windows. They’re great books but they’re old, often out of print
by ripley12 5y ago
There’s a real problem here: those are still the books to read if you really want to understand Windows. They’re great books but they’re old, often out of print, and the onus is on the reader to distinguish outdated info from still-relevant info. Yet as far as I can tell, nobody’s publishing better books about Windows programming today.
It’s remarkably hard in 2021 for a newbie to start learning Windows programming “properly”.
- no_time 5y agoIt's because MS treats win32 (or how ever you want to call the "legacy" api) like the plague despite it being the past,present and arguably the future. I still can't name a single UWP app that isnt a crude mockery of some win32 app that runs circles around it in both performance and UI design. My favorite example of how this new generation of MS devs handle performance: https://github.com/microsoft/terminal/issues/10362 https://github.com/microsoft/terminal/issues/10362
- ripley12 5y agoI think that’s an unfair characterization of the Terminal issue you linked, and the Terminal developers in general. If you follow the Terminal repo it is clear that the devs are not fans of the “modern” Windows technologies they are forced to work with.