4 ms·
Most of that is true (well, except for web frameworks bring great; I don't think anything about web development achieves greatness) but, where Apple is concerne
by uniqueid 5y ago
Most of that is true (well, except for web frameworks bring great; I don't think anything about web development achieves greatness) but, where Apple is concerned, much of the problem is the short release cycle they moved to about a decade ago.
It's not remotely worth it to me carefully to build a desktop app for a platform that I can't count on staying the same for more than a year.
Actually, it's not even a question of whether it's worth it; in some cases, it's physically impossible for a solo-developer to develop a large app on the shifting sand that is MacOS.
- bernardv 5y agoYes, I understand that. The applications I’m thinking of are those that either have a longer shelf-life and/or are business applications. In Finance, for example, many important vendors have been rolling-out trading front-ends based on web frameworks (maybe Electron for all I know). They are absolutely terrible, again, because of the lack of standard UI usability rules. Combine that with very poor documentation, and non-existent training and it’s a disaster.
- uniqueid 5y agoI emphatically agree with that. My complaint is that it feels like a hopeless battle to try and write good native desktop software today. Every year the OS's APIs and UI change... that means weeks or months tweaking your project every year until you end-of-life your app.
- pseudalopex 5y agoI think you exaggerate. Some native apps I use were last updated 5 or 10 years ago.
- uniqueid 5y agoThe ability to launch an old Mac binary is different than the Xcode project you used to build it being healthy. A developer can't open a ten year project and just submit it to the app store. Most likely it won't even build.