Inferno: Document the nature of performance gains over React

Created on 16 Sep 2016  Â·  15Comments  Â·  Source: infernojs/inferno

Hi there,

This looks like a very exciting project, and terrific work!

I'm curious what about the way Inferno is built makes it faster than React, and what sort of application characteristics will benefit most (or least) from these performance boosts.

I see a "Performance" section in the Readme but it doesn't explain why Inferno is any better than React. In fact, it mostly seems like an advertisement for React!

If such a section is to be written/expounded, it might be nice to include a comparison to Preact as well.

While benchmarks are likely to be helpful, explanations of the underlying algorithm changes and the nature of the changes (eg; "automatic shouldComponentUpdate" or "not rendering content on the screen", etc) is really what I'm looking for personally.

Thanks, and keep up the great work!

documentation enhancement

Most helpful comment

@rattrayalex This has been asked numerous times, so it's definitely going to happen. I actually plan on re-doing much of the README.md in general. Given Inferno 1.0 has a new API and many of the things that people want to understand (JSX vs non-JSX) really need to be documented better.

All 15 comments

@rattrayalex This has been asked numerous times, so it's definitely going to happen. I actually plan on re-doing much of the README.md in general. Given Inferno 1.0 has a new API and many of the things that people want to understand (JSX vs non-JSX) really need to be documented better.

Awesome, best of luck!

Feel free to close this issue if you'd prefer to keep track of it elsewhere (eg, in your head)

:hear_no_evil: I take the occasion in this issue to congratulate you for this great work.
Thank you!

Thank you @Nicolab :)
@rattrayalex I'll leave this issue open as a reminder!

I've been looking at inferno to understand is internals. A good technical piece would be great.

Let us know if there is something we can help with.

@nojvek if you'd be up for joining our Slack. I could go through some of the details there, otherwise there's a WIP gist here: https://gist.github.com/trueadm/3944f0aa1c1a6998257b80901ac1d152

(ping me at [email protected] if you want an invite)

@nojvek if you're considering writing something please take a look at the docs repo and consider contributing something! (https://github.com/infernojs/docs)

I'll work on this.

@trueadm update the guide in the /docs folder?

For now, I'll just add it to the README.md and then later at a long-note in the docs.

I feel like the level of documentation in the README for this is pretty high now. Opinions on closing?

I feel we should talk a bit about blueprint tricks used. That's where react
and inferno fundamentally differ right?

On Thursday, December 15, 2016, Luke Sheard notifications@github.com
wrote:

I feel like the level of documentation in the README for this is pretty
high now. Opinions on closing?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trueadm/inferno/issues/356#issuecomment-267496182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-JVBtklP2_p8mBBe9ZIutXlJHY1na7ks5rIe0agaJpZM4J-ka2
.

@nojvek Inferno no longer uses blueprints. Inferno and React use almost identical methods now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nassirdreffy picture nassirdreffy  Â·  4Comments

dessalines picture dessalines  Â·  4Comments

jdalton picture jdalton  Â·  3Comments

gajus picture gajus  Â·  3Comments

imetallica picture imetallica  Â·  5Comments