5 ms·
You missed more: web developers are plentiful and your one app runs on every system imaginable. Some web haters counter with the idea that if we had a common r
by selfmodruntime 4y ago
You missed more: web developers are plentiful and your one app runs on every system imaginable.
Some web haters counter with the idea that if we had a common runtime / sandbox, native could target any OS as well. They miss that the browser is literally just that.
- Turing_Machine 4y ago> Some web haters counter with the idea that if we had a common runtime / sandbox I remember when that was called "Java". :-) It didn't work out on the desktop.
- euroderf 4y agoSwing was sposta be the Great Desktop Hope. It turned out to be pretty clunky though IIRC. AWT too.
- 411111111111111 4y agoThe difference is that Java promised to be that, but wasnt in practice. The browser ultimately delivered on the promise
- tabtab 4y agoIt probably could have been fixed, but HTML browsers kept a step ahead in progress. Java applets lost the improvement pace race, but the applet concept has merit because it was designed for GUI's, unlike HTML. If applets had better up-front security, better version management and auto-updates (like current browsers do), and better download-modularity such that one didn't have to download the entire app to open one screen, for example. Oracle buying it didn't help, as they have a reputation for suing everything that moves.
- dragonwriter 4y ago> Some web haters counter with the idea that if we had a common runtime / sandbox, native could target any OS as well. But if you had a common VM, runtime library, and sandbox that was feature-competitive with browsers, you’d basically just have reinvented the browser platform, but without the ecosystem of existing code and developers.