by expression100 on 12/2/16, 3:22 PM with 128 comments
by cheapsteak on 12/2/16, 8:20 PM
by tzaman on 12/2/16, 5:24 PM
I click the link. Get to an under construction page. Click the link, get to Github, think "this is interesting" to myself. Read on. Find there's a project called Cerebral, which is a state management library for React/Inferno/Whatever. Start thinking there's something wrong with my app, that's "just" about to launch, and is "just" using plain old Redux. And now I'm thinking it's not good enough any more (while remembering I haven't even given a try to redux-saga), and maybe I should try another stack with Inferno/Cerebral?
Why are you doing this to me, JavaScript?
by chickenfries on 12/2/16, 4:43 PM
> Inferno is much smaller in size, 7kb vs 45kb gzip.
Given that you're building the kind of app that is complicated enough to require a state management library, a virtual dom implementation, etc... does this 38kb really matter? Is anyone really shipping commercial apps where 38kb on page load would be that meaningful of a performance gain? Especially if you're doing serverside rendering and requiring react asynchronously?
by trueadm on 12/2/16, 5:23 PM
Furthermore, if anyone has any questions feel free to ask away (I'm the author of Inferno). :)
by bsilvereagle on 12/2/16, 4:21 PM
by aargh_aargh on 12/2/16, 4:32 PM
by dirkg on 12/3/16, 1:59 AM
So there's no website. So what? The github page clearly explains what it is, who its for and how it works. Focus on the product, talk about its pros/cons without trying to distract from the core issues.
e.g. the size complaint - almost every article about React/Angular/Vue will compare the lib sizes and impact on loading etc - Inferno is faster and smaller. Why complain?
The focus of the library seems to be speed, a minimal implementation that is still fully API compatible with React, which is no mean feat. And on top of that it happens to be the fastest UI framework. Give some credit to the author, FB has already said they might be incorporating ideas from it.
by trueadm on 12/2/16, 11:40 PM
The team and I would love to hear from you. We want to make Inferno better and we believe in doing so, we can start a shift in the community that starts to realise that performance on mobile with the current state of libraries and tools is not good enough. This was always the primary goal for why I began Inferno – about 2 years ago.
by quickben on 12/2/16, 4:21 PM
by mstijak on 12/2/16, 9:09 PM
http://cx.codaxy.com/v/inferno/docs/examples/grid/dynamic-gr...
http://cx.codaxy.com/v/master/docs/examples/grid/dynamic-gro...
I think that inferno-compat parity with React should be Inferno's top priority now. The performance is already great.
by joobus on 12/2/16, 6:02 PM
by wheelerwj on 12/3/16, 6:17 AM
by wje on 12/2/16, 5:23 PM
by iamleppert on 12/2/16, 6:32 PM
Clearly, the authors don't have much experience in this regard to make such claims. Caveat emptor.
by coldcode on 12/2/16, 4:46 PM
by findjashua on 12/2/16, 6:59 PM
by JustSomeNobody on 12/2/16, 5:37 PM
by SamBam on 12/2/16, 4:59 PM
by spankalee on 12/2/16, 8:55 PM
by HugoDaniel on 12/11/16, 5:52 PM
by kimshibal on 12/2/16, 4:33 PM
by nkkollaw on 12/2/16, 11:28 PM
What does it mean to be React-like? Is it a drop-in replacement? Are React components compatible? Or it just looks like React (it does)?
I'm going absolutely crazy trying to keep up-to-date with all frameworks coming out nowadays.
Yesterday it was Svelte, today it's Inferno.
What's good about using this instead of React? 3k of parsing instead of 40k is a huge improvement, but can we still using stuff that was made for React?
I'm lost.
by iLoch on 12/2/16, 4:50 PM