4 ms·
Headline in in 20 years: Javascript UI library that is compiled into another javascript UI library and used in almost all desktop applications now for some rea
by MiddleEndian 4y ago
Headline in in 20 years:
Javascript UI library that is compiled into another javascript UI library and used in almost all desktop applications now for some reason now TWO million times slower than native desktop widgets. Here's why you should convert your native application to it anyway!
- deleted 4y ago[deleted]
- emkoemko 4y agonothing wrong with using javascript in the UI, is it that much slower? i mean GNOME uses it and i can bring up the js console on my OS, does not seem to make any performance difference then something written in C++ etc.
- anthk 4y agoYou are deluded if you think that. Even with DE's made with Mutter such as Budgie, the perf and smootness difference between the first and the second it's very noticeable. I would like Gnome if it supported Guile as the scripting language (now Guile 3 has a Jit) as an alternative to GJS.
- emkoemko 4y agowhat do you mean? not sure what your saying but i tried KDE and that was a slide show... GNOME is smooth i use it daily so yes JS is fine if its used in GNOME it proves it.
- ComputerGuru 4y agoI should think JS itself in the UI is "fine" if it's just JS we are talking about and not the DOM or other "web" technologies (a la Electron and co). After all, V8 is faster than the Python interpreter, and quite a lot of UIs are written in Python without it being a bottleneck - it's just a layer of glue pulling together various APIs and creating some sort of pipeline and none of the actual performance-sensitive stuff is done in the interpreted language either way (except when you're doing things like calculating stuff or sorting the contents of widget in Python or JS, etc. where inefficiencies in your code and in the language you are using begin to show - but those aren't strictly required to be part of your UI markup).