2 ms·
Unpopular opinion: Please not another builtin high-level UI for the web, none of the native platforms got their 'system UI' right either, and there will never b
by flohofwoe 8y ago
Unpopular opinion: Please not another builtin high-level UI for the web, none of the native platforms got their 'system UI' right either, and there will never be a single UI solution for all problems.
Radical, overly optimistic suggestion: Reduce the browser to 2D+3D canvas, audio (not WebAudio please, too over-engineered), input, networking (...) and implement everything higher level on top of those thin platform abstraction APIs in JS+wasm modules that are loaded ond demand. Put the current HTML APIs into such modules as well for backward compatibility.
- kaoD 8y agoThat's a terrible suggestion. We need markup. We need standard markup. We need accesibility. We need semantic tags. We need interoperability. We need developer tools. We don't need N+1 "standards". We don't need N*2 developer tools. We don't need N^2 teams working on subpar competing "platforms". We need HTML.
- flohofwoe 8y agoThe HTML standard would be implemented in a module, which could even be bundled with browsers so it doesn't need to be downloaded on first use. Nothing would change for HTML usage except that it wouldn't be baked into the browser executable, and alternatives to HTML could be explored without bloating the browser even more. The devil is in the details of course, that's why I wrote "overly optimistic" :)
- madeofpalk 8y agoI mean, Canvas is there. You're more than welcome to draw your own UIs in it, as plenty have done/tried before. Flipboard had a render-react-to-canvas project they used for mobile (which was completely inaccessible to any sort of assistive technologies), but I believe they abandoned it.
- flohofwoe 8y agoI kind of did and it works quite well. Fair point about accessibility though. Another problem is that there's no way to access system font data from WebGL. Also the way I'm currently doing rendering (continuous frame rendering even if the UI doesn't change) isn't mobile-friendly. But these are all solvable with a few more resources thrown at it (Dear ImGui is a single-developer-project, and the cross-platform rendering library (sokol-gfx) too. http://floooh.github.io/oryol-sticky-tests/imgui-highdpi-sapp.html http://floooh.github.io/oryol-sticky-tests/imgui-highdpi-sap... This is 460 KByte wasm, 260 KByte of this is embedded TTF font data.
- dmitriid 8y agoWow. Your library is simply amazing. Especially considering it's a single-developer project.
- gitgud 8y agoInteresting idea, so you're proposing different standards of HTML for different web apps? Seems like added complexity for simplified app development