4 ms·
The thing that holds many web UI's back is the web/html DOM and the respective CSS recalculations. You get get close to 1000x performance on web apps if you mak
by graiz 4y ago
The thing that holds many web UI's back is the web/html DOM and the respective CSS recalculations. You get get close to 1000x performance on web apps if you make sure the DOM will never cause a UI block or re-computation on the layout. The web is great for simple apps but if you're building anything complex you have to play a bunch of tricks to get web UI to work. Going full GPU and building your own controls is certainly possible but I'm hoping there's a middle ground.
- The5thElephant 4y agoThis would be way easier if everyone didn't default to using React or even worse React-Native-Web. Not only do you have to deal with handling CSS recalcs (not so bad on its own), you also have to deal with React rerendering the entire DOM when you don't want it to and then the layers of div-soup and absurd style abstractions React-Native-Web uses. Tauri + Vue/Svelte/Solid/Etc seems like a great way to build a decent desktop and web app, but you just don't have teams picking anything but React React React React.
- pjc50 4y agoDo we have "transactional" DOM yet? The ability to batch up a bunch of stuff and then hit the UI update.
- bartq 4y agoWe could have amazing HTML/CSS performance if we had programmable "HTML to bitmap" caching. But: a) it's not secure if we can render HTML to bitmap and send over network, b) cache invalidation problem - we'd have to invent mechanisms to lock HTML against further changes or track changes and rerun "HTML to bitmap" procedure. All this is not suitable for web, but for thing like Elector - hell yeah. HTML to bitmap extension would be really welcome. Then you could render UI in WebGL or WebGPU. Adobe Flash had something similar if I recall correctly.