Inferno seems to be very comparable to Riot.js, only Riot is more mature, has event delegation and a router, and is only 9.5k vs Inferno's 7k. And riot has an actual web page.
InfernoJS – A JavaScript library for building powerful user interfaces
51–60 of 135 posts
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#52Inferno seems to be very comparable to Riot.js, only Riot is more mature, has event delegation and a router, and is only 9.5k vs Inferno's 7k. And riot has an actual web page. http://riotjs.com/
last I checked, Inferno was a React "near drop-in" replacement. So not the same at all, unless you look at it in a vacuum.
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#53Earlier quoted context omitted.
What do you think the extra 38kb of code is for? My point of view is, you've got a company with thousands of employees who work with a library every day and core teams dedicated to its improvement. Their requirements for speed and bandwidth far exceed our own as they reach further into the nth percentile of users, so you know things like speed and bloat are important for them to cut out. What, if anything, is actuall…
There's far more to Inferno than just file size. The internal implementation is completely different. Furthermore, React Fiber and Inferno are very different in terms of internal approach.
Thanks for your reply Dominic. As an end user, what should compel me to use Inferno for any production purposes? Bearing in mind React has the support of multiple billion dollar companies, several targets (web, native mobile/desktop, console) and a community of what is sure to be tens if not hundreds of thousands of developers. I just don't see the benefit of incremental improvements when they're not being integrated into that community. You lose all the benefit. I have no doubt Inferno is faster, but I suspect you're being disingenuous when you say all the same features are available.
The trouble I have is not specific to Inferno, but rather the idea that less and new is better. Eventually, your users will want something that Inferno doesn't offer, and eventually it will be implemented. And this will happen more than once, probably to the point where your library, too, is 45kb. So is all this work and fragmentation and confusion and comparing of benchmarks really worth it? I think not, unless the technology stands to bring something vastly different to the table.
The trouble with competing with React in its own space right now, stems from the vast amount of resources many of companies are putting behind it. You just can't make a Inferno Native, etc. I think we'd be much better off all working together on new ideas, not rehashing innovation in order to win benchmark tests.
All that said, I applaud the effort, as I'm sure this took a lot.
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#54It's disingenuous for the authors to claim this is a near "drop-in" replacement for React. Just because it works now for (likely) some limited surface area test app doesn't mean it will work in all of React's weird nooks and cranes, or its constantly changing APIs or huge stack of dependent behaviors it has inherited from its ever-changing dependencies.
Clearly, the authors don't have much experience in this regard to make such claims. Caveat emptor.
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#55It's disingenuous for the authors to claim this is a near "drop-in" replacement for React. Just because it works now for (likely) some limited surface area test app doesn't mean it will work in all of React's weird nooks and cranes, or its constantly changing APIs or huge stack of dependent behaviors it has inherited from its ever-changing dependencies. Clearly, the authors don't have much experience in this regard t…
That's why I claim near rather than perfect. It's a constant work in progress, that's the challenge :)
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#56It's disingenuous for the authors to claim this is a near "drop-in" replacement for React. Just because it works now for (likely) some limited surface area test app doesn't mean it will work in all of React's weird nooks and cranes, or its constantly changing APIs or huge stack of dependent behaviors it has inherited from its ever-changing dependencies. Clearly, the authors don't have much experience in this regard t…
[deleted]
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#57Here we go again. 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…
Don't try to surf the tech wave. Learn to swim.
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#58Earlier quoted context omitted.
These days, JS parse time on mobile devices is more important than file size. And that isn't even necessarily file size specific - Nolan Lawson did a comparison of the different methods used to bundle JS to show how they can have a huge impact: https://nolanlawson.com/2016/08/15/the-cost-of-small-modules...
Still does 38kB really matter if the rest of your app requires parsing of several hundreds of kB of JS?
If you're bundling it into one payload it does not. If you're code splitting, it's 38k of download time and ~120k of parse time you're not paying on time to first meaningful paint. It's a couple dozen ms on desktops but can be several hundred on mobile.
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#59Earlier quoted context omitted.
Is it JavaScript that is doing this to you? I think it's you doing this to you.
Failed attempt of being funny aside. The struggle is real for many developers. Many (if not most) of us are self-taught and we like to explore how deep the rabbit hole goes, which inflicts many episodes of analysis paralysis upon us, and it takes a lot of willpower to stay on course. The fear then becomes what if any given choice will be obsolete once we launch our products, given how fast the technologies move forwa…
I think this is spot on. And is hard to understand while working for yourself and thinking your knowledge may become obsolete if you don't know the latest trending tech.
Re: InfernoJS – A JavaScript library for building powerful user interfaces
#60Considering the lifetime of JS frameworks nowadays, the website has been "coming soon" for ages. http://web.archive.org/web/*/http://infernojs.org/
They just went through a big github discussion about the design that finished last Saturday. It should be actually pretty soon instead of "soon".