+1. This was exactly the reason for once - DOM diffing without any intermediate data structureshttps://github.com/utilise/once
-
-
Replying to @pemrouz @slightlylate and
"DOM is slow" was hugely misleading. DOM is not slow to walk, or read. Updates may be slow. Vdom is just buzzword for memoization.
2 replies 0 retweets 3 likes -
Replying to @pemrouz @slightlylate and
Also 2-3x as fast on their own benchmark at fraction of the size :) https://mathieuancelin.github.io/js-repaint-perfs/ …
1 reply 1 retweet 0 likes -
Replying to @pemrouz @slightlylate and
That benchmark has been broken for a long time. It's extremely easy to "cheat", just like most benchmarks are.
3 replies 0 retweets 6 likes -
Replying to @trueadm @slightlylate and
I don't disagree, but this standard was presented React conf, trashed angular/ember on stage. Now it's broken? Which benchmark is better?
3 replies 0 retweets 0 likes -
Replying to @pemrouz @slightlylate and
It wasn't presented by the React team though. I think there was a lot of miscommunication over dbmonster
1 reply 0 retweets 2 likes -
Replying to @trueadm @slightlylate and
It was React conf lol. If Google trashed React on stage at one of their conferences, the response would be very different..
2 replies 0 retweets 0 likes -
Main thing is React is guilty of moving goal posts, fallen behind on all initial main claims, now the responses are "well, actually.."
1 reply 0 retweets 0 likes -
Replying to @pemrouz @slightlylate and
I know it was a React conference. I'm speaking as the React team though - we don't trash other frameworks. We support competition.
2 replies 0 retweets 6 likes -
Replying to @trueadm @slightlylate and
This pattern of behaviour is very common with team+cmty. Propagate half-truths when React stands to benefit, then caveat when it backfires –
2 replies 0 retweets 1 like
It ultimately all comes back to being true believers about the importance of the "FP" paradigm shift.
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.