Don't get me wrong; I actually appreciate the breakdown. It just makes me not want to even consider native Windows development. This is definitely an example of too many choices being a very bad thing.
This reply stuck in my head and bothered me enough that I am back several days later to tell you about it.
First, blaming this on developers is simply a bad take. Developing a native app shouldn't be a purity test. Electron and friends clearly offer a path of least resistance, even if it is deeply flawed. The decision to use it and accept the tradeoffs is just as pragmatic for the solo greenfield dev as it is for the many who are told by their employer to use the cheapest, fastest option.
No, if there is a fault, it is squarely on the shoulders of Microsoft for not successfully executing and sticking to their promises. Developers and companies are effectively investing in Microsoft's integrity when they decide to accept that the latest framework is truly the final form, and they've been let down over and over by them.
Second, defending the state of development on Windows as fine because everyone else is doing it is just... kind of lazy while being totally irrelevant to the larger question of how to develop native apps on Windows.
I'm annoyed because this comment really and truly feels like an example of why we can't have nice things.
Don't get me wrong; I actually appreciate the breakdown. It just makes me not want to even consider native Windows development. This is definitely an example of too many choices being a very bad thing.