4 ms·
The main reason is because we shoehorn complex apps/ui's into a browser that wasn't made for it. It's not the UI is very complex , or that there are ton of fra
by brimstedt 4y ago
The main reason is because we shoehorn complex apps/ui's into a browser that wasn't made for it.
It's not the UI is very complex , or that there are ton of frameworks with different maturity levels.
It's because the browser and thus html/CSS was made for documents.
If we made a "browser" made for apps, where we didn't need to transpile to js, and didn't need to cater for incompatible browser versions, but could concentrate on what really matters we wouldt have such a big problem
- chrisco255 4y agoYou could do this now with HTML canvas and web assembly, but you won't, because the web already has a rich feature set of accessible and search engine friendly features. > but could concentrate on what really matters we wouldt have such a big problem Curious for someone who dismisses the complexity of front end, what you think really matters in creating a cross platform UI application experience that works on all devices?
- rrrrrrrrrrrryan 4y agoI'm old enough to remember when Flash and Java were hailed as the future of application development because they were "cross platform." Your "browser made for apps" isn't the dream you're imagining - today's SPAs are miles better, whether they run in-browser or are packaged up as Electron apps.
- steve1977 4y agoSo, something like Java applets?