Benchmarks showing that VDOM is somehow magically faster than DOM are nearly always suspect; case in point: https://github.com/marko-js/marko-vdom/pull/5 …https://twitter.com/slightlylate/status/901603718843457536 …
-
-
Replying to @slightlylate
BTW, I'm not bagging on VDOM or those who like it; I'm just asking for everyone to be honest their motives and the costs we impose for them.
2 replies 0 retweets 6 likes -
Replying to @slightlylate
All of computing is built on going slower than hardware to let the humans catch up; it's often how we define "progress". C'est la vie.
1 reply 1 retweet 2 likes -
Replying to @slightlylate
The question for us as engineers, however, is _can we afford those costs_ in a specific scenario? If not, it's *bad engineering* to pay them
2 replies 0 retweets 2 likes -
Replying to @slightlylate
How many resources do you want to put in determining what is appropriate? Answer might depend on if you are methodological or opportunistic.
1 reply 0 retweets 0 likes -
Replying to @jdisney
A good baseline for today's web is "can I get TTI below 5s on http://webpagtest.org/easy ?"
2 replies 0 retweets 1 like -
Replying to @slightlylate @jdisney
That's a hard test: probably < 150k of critical resources (on the wire), exec on slow CPUs
1 reply 0 retweets 0 likes -
Replying to @slightlylate @jdisney
And even that is luxurious compared to what many users will experience over flaky networks and *really* cheap devices.
1 reply 0 retweets 0 likes
Basically, you probably can't afford today's most popular frameworks; they were built for desktop and it shows
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.