4 ms·
The web works fantastic in a browser but it seems like as soon as you try and port it to a native mobile application or desktop application; you can tell there
by joeblau 11y ago
The web works fantastic in a browser but it seems like as soon as you try and port it to a native mobile application or desktop application; you can tell there is a performance difference from native code.
- creshal 11y agoWe only put up with shitty performance on the web because we're used to it. We expect proper performance for actual programs.
- legulere 11y agoThere's actually two problems: javascript vs. machine code generated from c (or a c-like) rebuilding UI elements in HTML and rendering them with a browser engine vs. native UI toolkit. Often in comparisons the emphasis is only on the first one, and the difference usually isn't that big (maybe a factor of 2). The real issue actually is the second problem, it's much worse. That's also why I find the trend to do user interfaces in HTML so terrible: native UI toolkits work better and use less resources. The only advantage is that they run everywhere, but so does drawing into a 2D pixel matrix and rendering it.
- creshal 11y agoIs "run everywhere" really still a problem? Qt e.g. works on everything from Windows to bare metal embedded Linux framebuffers to iOS devices.