Main thing is React is guilty of moving goal posts, fallen behind on all initial main claims, now the responses are "well, actually.."
-
-
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 -
@floydophone "DOM is slow",@leeb on O.o (https://github.com/rijs/fullstack/issues/14#issuecomment-74127669 …),@ryanflorence dbmon perf, etc. Would be great to see more consistency2 replies 0 retweets 0 likes -
Re: "DOM is slow", agree w/ everything
@trueadm says, stand by my prev talks, also wanted to remind you React was conceived in IE8 era2 replies 0 retweets 2 likes -
Replying to @floydophone @trueadm and
Pedram Emrouznejad Retweeted Pedram Emrouznejad
See https://twitter.com/pemrouz/status/901791314240557057 … and also benchmarks. It's empirically false.
Pedram Emrouznejad added,
4 replies 0 retweets 0 likes -
There was another perf claim about faster-than-manual-DOM in the narration iirc which refers to getting fastdom-style batching by default
1 reply 0 retweets 1 like -
Replying to @floydophone @pemrouz and
I stand by this. Look at how different adtech products interact with each other to ruin the user experience. Unique to React? Nope.
1 reply 0 retweets 1 like -
Replying to @floydophone @pemrouz and
But having a framework coordinating this across components built by different teams is a huge advantage.
2 replies 0 retweets 1 like -
Replying to @floydophone @pemrouz and
Like I said, best case you get scheduling wins. What most are paying for that, today, is fundamentally unsustainable on mobile. Tradeoffs!
3 replies 0 retweets 2 likes
Scheduling wins have huge macro effects. Shrinking the size of scheduling coordination is how to get better on mobile.
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.