Interview with the author of React-like Inferno about JavaScript optimisations
1–10 of 51 posts
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#2Sadly, this article has nothing to do with an inferno OS port to js.
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#3I misunderstood the title and was very confused as to why Dan Brown would have things to say about Javascript perf.
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#4Sadly, this article has nothing to do with an inferno OS port to js. http://www.vitanuova.com/inferno/
Agreed and similarly disappointed. Can we please change the title to point out that this is specific to ReactJS?
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#5Re: Interview with the author of React-like Inferno about JavaScript optimisations
#6Sadly, this article has nothing to do with an inferno OS port to js. http://www.vitanuova.com/inferno/
Agreed and similarly disappointed. Can we please change the title to point out that this is specific to ReactJS?
This has nothing to do with React. This is a JavaScript library called Inferno – the title makes sense to people in the JavaScript scene.
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#7You'll have to excuse my ignorance as I just like to lightly follow the JS web dev community and am no way a JS expert, but what is the reasoning behind the React spin-offs? There's Inferno, Preact, ivi, and possibly more, but are all of these so different that they require their own repository? Is it out of the question to simply contribute to the other existing open source projects? I imagine there are some backwards compatible breaking changes but it feels a bit weird to have so many React-like spinoffs. Could anyone shed a light on this? I'm genuinely curious.
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#8You'll have to excuse my ignorance as I just like to lightly follow the JS web dev community and am no way a JS expert, but what is the reasoning behind the React spin-offs? There's Inferno, Preact, ivi, and possibly more, but are all of these so different that they require their own repository? Is it out of the question to simply contribute to the other existing open source projects? I imagine there are some backwar…
React as an API is brilliant. A Couple of methods only. The libraries conform to the API and achieve different things. Preact is react but simple. It's very lightweight, readable and gets the job done. Inferno is heavily optimized at the cost of readability. React is the original project which is now a monolith. Smaller than angular but still big.
Remember on average every 1Mb of JS Will take about a second to parse and initialize. Smaller, we'll architected libraries like preact and mithriill means you can make pages load within a blink of an eye.
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#9You'll have to excuse my ignorance as I just like to lightly follow the JS web dev community and am no way a JS expert, but what is the reasoning behind the React spin-offs? There's Inferno, Preact, ivi, and possibly more, but are all of these so different that they require their own repository? Is it out of the question to simply contribute to the other existing open source projects? I imagine there are some backwar…
Note: I'm the author of Inferno and know the authors of Preact and Ivi well.
That's a great question and one I frequently get asked. The "current" React codebase is legacy in many ways, the React team are hard at work on React Fiber which is complete re-write of the entire codebase.
The legacy codebase isn't something we can actively make better (I've had my PRs merged though) without a huge rewrite. If we tried to make changes, it would break React for many people due to how coupled many things are.
A lot has changed in the last few years and the approach to virtual DOM has been one of them. Going forward, the React team are making big efforts to change this.
Re: Interview with the author of React-like Inferno about JavaScript optimisations
#10You'll have to excuse my ignorance as I just like to lightly follow the JS web dev community and am no way a JS expert, but what is the reasoning behind the React spin-offs? There's Inferno, Preact, ivi, and possibly more, but are all of these so different that they require their own repository? Is it out of the question to simply contribute to the other existing open source projects? I imagine there are some backwar…
React as an API is brilliant. A Couple of methods only. The libraries conform to the API and achieve different things. Preact is react but simple. It's very lightweight, readable and gets the job done. Inferno is heavily optimized at the cost of readability. React is the original project which is now a monolith. Smaller than angular but still big. Remember on average every 1Mb of JS Will take about a second to parse…
Inferno is 8kb, it's smaller than the Mithril re-write and is on par with Preact in terms of parse performance. I think you may have looked at the older Inferno codebase, as the current one is very slim and readable.