3 ms·
Context matters. If you're building essentially square box with interactions (essentially flash) , it would probably be fine. But if you're trying to optimize
by Tobani 7y ago
Context matters. If you're building essentially square box with interactions (essentially flash) , it would probably be fine.
But if you're trying to optimize across several displays HTML can re-flow for you and isn't generally terrible unless you're doing things that need to be pixel-perfect.
- tabtab 7y agoI believe we need 3 different UI standards: 1. Page and document centric (HTML may be close enough) 2. Productivity and data-oriented GUI's ("cubicle" stuff) 3. Games, art, and diagrams Doing everything in HTML/CS/JS keeps proving too clunky. Even the big wealthy sites have odd rendering bugs that pop up.
- Tobani 7y ago> Doing everything in HTML/CS/JS keeps proving too clunky. Clunky, sometimes sure. It has largely been fine in my experience. > Even the big wealthy sites have odd rendering bugs that pop up. This will always be the case.
- tabtab 7y agoRe: It has largely been fine in my experience. That's not my experience. It requires too much fiddling and diddling to get things right that wouldn't be drama under 90's GUI IDE's. (Early versions sucked, but they got better with time.) Maybe a few experts somehow master all the arcane CSS/DOM rules, but that's the exception. Arcane fiddling may be great job security, but it's not economically logical on a planet-wide view.