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?
-
-
Replying to @Jonathan_Blow
Honest question, what if you need clip by path (aka border-radius + overflow: hidden) + 0.9 opacity + box shadow + let's say blur on hover + transition of all of that. Suddenly it's really hard to do even 60fps, or is there a simple way?
6 replies 0 retweets 6 likes -
Replying to @cztomsik @Jonathan_Blow
I think the disconnect here is that you are assuming that the specification for the effect you wanted had to come from CSS/HTML. That does take a monumental engineering effort, because you are basically writing a hard-core optimizing compiler for vague descriptors :)
1 reply 0 retweets 9 likes -
But if instead you just asked, how hard would it have been to render the page if it were described in a _good_ graphical description that were not insane and ill-defined like CSS/HTML, the answer is that your example could easily be done at 60fps on a modern CPU alone.
2 replies 0 retweets 16 likes -
So it's very important to understand the specific complaint. The complaint is not that the browser authors are somehow failing to provide high performance given existing inputs. It's instead that this entire system needs to be redesigned to produce the same output efficiently.
1 reply 0 retweets 15 likes
And the fundamental reason why we don't have this is, I think. precisely the gravamen of Jon's original tweet. If people understood just how fast web pages _should_ render, maybe we would not have ended up with the CSS/HTML disaster that now makes high-performance very difficult.
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.