Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it dead? #436

Open
haggen opened this issue Jul 20, 2017 · 9 comments
Open

Is it dead? #436

haggen opened this issue Jul 20, 2017 · 9 comments

Comments

@haggen
Copy link

haggen commented Jul 20, 2017

Last commit was more than a year ago. How's the future of this project looking? Any prospects?

@iambumblehead
Copy link

https://infernojs.org/

inferno works in all the same places virtual-dom does and more. its also faster, has a simpler interface with fewer parts to manage and can be used to render svg as a normal out of the box ability. Development is active and maintainers are pro-active about merging in pull requests and responding to issues.

@haggen no one has responded to your comment for almost one month and there are 48 old un-merged pull requests.

@haggen
Copy link
Author

haggen commented Aug 14, 2017

Thanks for the reply @iambumblehead, but what you suggested is not quite the same. I just want the virtual dom part. Inferno (core only) has 110KB+ while this has around 45KB.

@iambumblehead
Copy link

@haggen I didn't realize there was such a great difference in size.

Some experiences I've had that may be useful to you... I replaced virtual-dom with inferno in a web video-editing application and noticed observable performance improvements right away. I used snabbdom and morphdom as well, but found both to be less accurate/detailed in the adjustments they made when publishing a vtree compared to either inferno or virtual-dom.

Of those libraries, virtual-dom was the most accurate and inferno is the next most accurate. Morphdom was least accurate.

By 'accurate' I mean that snabbdom and morphdom tend to replace entire node hierarchies in the wrong way and they tend to replace the entire node, whereas virtual-dom or inferno would instead affect minimal changes redefining specific node attributes or textContent only.

@haggen
Copy link
Author

haggen commented Aug 14, 2017

Hey thanks a bunch for the remarks, really helpful, much appreciated!
I'll be looking further into Inferno and React for now.

@jamesamcl
Copy link

I'm still using vdom in a large project without any issues. Porting to inferno would take time, and I've no particular reason to. I see vdom as more "finished" than "dead".

@rolfen
Copy link

rolfen commented Aug 20, 2017

Thank you for all the constructive suggestions.

@AlexGalays
Copy link

AlexGalays commented Nov 15, 2017

Another great lib that we're using: snabbdom
It's fast, modular (you can augment the syntax of h() with your own modules) and very, very tiny.

@DanielRuf
Copy link

Bump.

@Berkmann18
Copy link

It looks dead but finished to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants