How many web developers understand that a low-end integrated GPU on a laptop can draw full 4k screens of pixels at 3000 frames per second?
-
The problem is that it's never in isolation. To use your paste example, a paste operation can happen in the context of the current input element you're focused on, or a whole document, or other things happening in the upper stacks of the app.
An empty screen sure. You can fill that even on the CPU. If you need to layout 2000+ nodes with many of those being text nodes, that need special layout conditions for different types of fonts and languages, it becomes a little more complicated. That's before you do any JS.
But like, when I press a key, you also need to know what input element that is meant for, in order to have a UI at all? I'm sorry but you are not making any sense here.
-
-
That's what generic UI frameworks abstract away from you. If you did that from scratch, it'd maybe be simpler for your specific use-case and faster, but pile on top all the other things that a generic UI framework does for you, you get slower and more bloated.
-
Citation required on that last part. Are you sure the "slower and most bloated" part doesn't just come from the way people have programmed these things? I mean, you know that we did UIs just like this in the 1990s, and today's laptops are supercomputers compared to then?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.