Rax – A universal React-compatible render engine
21–30 of 42 posts
Re: Rax – A universal React-compatible render engine
#22Re: Rax – A universal React-compatible render engine
#23Re: Rax – A universal React-compatible render engine
#24Is it faster than Inferno[1]? [1] Inferno seems to be the fastest React drop-in replacement at 9kb size at the moment: http://stefankrause.net/js-frameworks-benchmark4/webdriver-t... - full post to the comparison table before: http://www.stefankrause.net/wp/?p=316
Re: Rax – A universal React-compatible render engine
#25Am I the only one finding it weird that they call it a render engine?
Re: Rax – A universal React-compatible render engine
#26Re: Rax – A universal React-compatible render engine
#27Interesting that they don't compare it to preact: https://github.com/developit/preact
reading that, it seems pretty good. Are there performance costs to its diffing against the "real" DOM? 3kb for "React" is pretttttty tempting
But I'm currently using Preact (server-rendered) for my personal site and loving the speed and byte size.
Re: Rax – A universal React-compatible render engine
#28Earlier quoted context omitted.
reading that, it seems pretty good. Are there performance costs to its diffing against the "real" DOM? 3kb for "React" is pretttttty tempting
Forget about file size, 40kb vs 8kb doesn't really matter in the modern era. If anything, using an obscure library may cost you more because it's less likely to be a CDN cache hit for the user.
Re: Rax – A universal React-compatible render engine
#29Good to see compatible implementations. Over time, we'll have something React-like as part of the web standards.
Hell no. High-level APIs should remain in user space, they are too often optimized for short term thinking, prone to breakage, and inefficient.
Most of the current DOM specification has been around since 1998-2000, and the spec hasn't made a single breaking change. Standards committees have an obligation to not break the foundations of the web, framework authors can do whatever.
Re: Rax – A universal React-compatible render engine
#30Earlier quoted context omitted.
reading that, it seems pretty good. Are there performance costs to its diffing against the "real" DOM? 3kb for "React" is pretttttty tempting
Forget about file size, 40kb vs 8kb doesn't really matter in the modern era. If anything, using an obscure library may cost you more because it's less likely to be a CDN cache hit for the user.
On mobile it's not just the file transfer that takes time: it's the JavaScript parsing and execution (on a single core) that hurts too. iPhones are massively faster than Android (especially cheaper Androids) at this, so many developers don't realize how much performance cost there is for a growing majority of their users.
Given how many different versions there are of popular libraries I'm personally skeptical that CDNs give you much of a chance if the asset being preloaded from another site. I'd love to see real numbers on this though.