3 ms·
Good luck running you GUI from know in a browser in ten years or maybe even five. Not to mention that WebGUIs are slow compared to native ones. https://news.y
by croes 3y ago
Good luck running you GUI from know in a browser in ten years or maybe even five.
Not to mention that WebGUIs are slow compared to native ones.
https://news.ycombinator.com/item?id=36446933 https://news.ycombinator.com/item?id=36446933
- zamadatix 3y agoBrowsers have extremely good backwards compatibility, five or ten years should really not net you any problems. They do carry quite a bit of bloat however, though so do most native toolkits these days.
- croes 3y agoFor old features yes, for new ones it depends. https://github.com/philipwalton/flexbugs https://github.com/philipwalton/flexbugs And there could be changes because of security concerns like with alert (), prompt() and confirm().
- c-hendricks 3y agoJust FYI, most (all?) of those are in years-old versions of evergreen browsers, no affected versions listed are supported I don't think.
- bobthepanda 3y agoThe problem with native has always been that * Users expect consistency within their apps, and will complain loudly if platform A has something that platform B has not * the native platforms’ rendering technologies are so different that you basically need a developer or team dedicated to each platform, with their own test infrastructure, etc. * even if you can afford to do the above, herding four teams using different technologies to do a coordinated feature release schedule is like herding cats In any case the native platforms hardly do much better. There are plenty of Windows, Mac, Android, iOS applications from ten years ago that don’t work well today, for instance.