4 ms·
Web UI is fine for web applications, obviously. But for desktop applications it is bloated, a big attack surface. HTML/CSS is made for online documents, and u
by jenadine 5mo ago
Web UI is fine for web applications, obviously.
But for desktop applications it is bloated, a big attack surface.
HTML/CSS is made for online documents, and using it for applications is a bit hack that happen to work, but hides a huge ton of complexity behind frameworks and frameworks of frameworks with leaky abstractions and each their own caveat.
- tapirl 5mo agoweb UI is slow, this is only reason when I don't it.
- thomashabets2 5mo agoI'm not a frontend developer, but seems fast to me. I'm surprised that the UI portion of this example takes so little CPU: https://youtu.be/7k0JNT6itaI https://youtu.be/7k0JNT6itaI Now, the rest of the DSP code sure is faster in native. What are examples where web UI is too slow for you? Or do you mean large apps written in JS, which is a different topic?
- tapirl 5mo agoSlow means many: * long program launch times * inconsistent frame rates during runtime * noticeable lag in user interaction
- thomashabets2 5mo agoThat's neither examples nor a clarification if you're talking about JS or WASM.
- tapirl 5mo agoNo specific examples. Just general GUI apps.
- ngruhn 5mo ago> a big attack surface Wdym? At least web apps are sandboxed by default in contrast to native.