3 ms·
The browser standards are behind. The img tag is wonky considering the various screen sizes and bandwidth variability today. Loading fonts is sketchy and weird.
by jbob2000 6y ago
The browser standards are behind. The img tag is wonky considering the various screen sizes and bandwidth variability today. Loading fonts is sketchy and weird. Anything to do with video is terrible. Anything to do with networking is terrible.
React and its ecosystems of libraries turn the browser in to something you can actually get stuff done with. Sure, it's a monster. But your codebase would be as well if you tried to fix all the janky crap in the modern web.
I don't want to program all my logic somewhere else. Front ends run on the client computer, I can keep one client's heavy computations separate from another client and it doesn't cost me anything. Fat front ends are the defence against expensive cloud providers or unstable self-hosted services.
- DaiPlusPlus 6y ago> img tag is wonky considering the various screen sizes and bandwidth variability today. The srcset attribute is well-established. And please elaborate on the issues you’ve experienced with HTML5 video. Every platform supports AVC1 now, even Firefox.
- jbob2000 6y ago> The srcset attribute is well-established. on new browsers > Every [new] platform supports AVC1 now, even Firefox.
- timw4mail 6y agoReact/Angular/Vue/etc. is the janky crap. The client side is MINE, stop wasting MY resources for your ease of development. I say this as a developer that has to deal with "React apps" at work. As I user I can't stand the "modern web" where megabytes of Javascript are wasted turning a page load into a spinner that doesn't work half the time.