3 ms·
Not to detract from the positivity of sweet new tech, but it's worth noting that "React outperforms Blaze when many elements change and Blaze outperforms React
by rtfeldman 13y ago
Not to detract from the positivity of sweet new tech, but it's worth noting that "React outperforms Blaze when many elements change and Blaze outperforms React when few elements change" is the same as "React outperforms Blaze in cases where the user is capable of noticing a performance difference", which reduces to "React outperforms Blaze."
Nevertheless, seriously appreciate the detailed and informative response. :)
- imslavko 13y agoDoes it mean that, theoretically, Blaze will still outperform React on a long series of small quick updates conducted by a lot of disconnected events?
- myhf 13y agoI'll have to see how each one handles a big grid of rotating colored circles with numbers on them in order to make an informed decision.
- ZeroGravitas 13y agoThat might be true, but it doesn't automatically follow. Java often gets dinged for startup time that it might make up for on longer runs and browser vendors seem to be sniping that their rivals are focussing on long term benchmarks at the expense of realistic workloads.