6 ms·
Introducing Inferno 1.0
- wsh91 10y agoWas I the only one who saw the title and thought of https://en.wikipedia.org/wiki/Inferno_(operating_system) https://en.wikipedia.org/wiki/Inferno_(operating_system)?
- inetsee 10y agoYes. It might help if they referred to it as Inferno-UI.
- gpapilion 10y agoThat was exactly what I thought. I was interested to hear about further Plan 9 developments.
- tonyjstark 10y agoAbsolutely. I was confused by the version number but otherwise happy to see something happening with Inferno. Then the disappointment...
- expression100 10y agoThankfully it wasn't about the movie – that certainly was a disappointment!
- expression100 10y agoThere's a lot of traction for Inferno – the JavaScript UI library lately, so I was pretty sure this had nothing to do with the OS. It's a shame the operating system couldn't have a nice logo like the JavaScript library though!
- expression100 10y agoGreat work! I'm so excited to use Inferno now it's finally out of beta and stable :)
- hectorchong 10y agoexcellent!
- ohstopitu 10y agoAs a beginner to JS frameworks (and a medium proficiency), is it advisable to skip React and target to learn Inferno instead?
- untog 10y agoNo. But the good news is that Inferno is extremely API-compatible with React (deliberately so, and has an inferno-compat package to help further) so should it stick around and continue to be this much more performant than React, switching should be relatively easy.
- badthingfactory 10y agoFor learning purposes, I would advise sticking with React. Being more mature, you'll likely be able to find answers to your questions more easily. Pluralsight, for example, has lots of great courses on React but none on Inferno. Knowledge will be highly portable between the two so if you find a need to switch over to Inferno at some point you won't have any trouble.
- pjmlp 10y agoYes, because in a few months it will be topping the HN headlines on how everyone is porting their applications to it.
- aarpmcgee 10y agoI think that seems unlikely, if only for the fact that React has a path for developing native apps. Writing shared business logic in Redux and allowing both DOM and RN seems like a slam dunk to me.
- deleted 10y ago[deleted]
- niftich 10y agoThere was a good interview [1] with Dominic, the author, a month ago, where he covered much of the design rationale behind Inferno. And he's on HN [2], and his comments often offer valuable insight as well. In a strange twist, he also just joined Facebook to work on React [3], so some of his ingenuity will find its way into React in the future. Meanwhile, Inferno is now run by a team of core committers [4]. [1] https://news.ycombinator.com/item?id=13160757 https://news.ycombinator.com/item?id=13160757 [2] https://news.ycombinator.com/threads?id=trueadm https://news.ycombinator.com/threads?id=trueadm [3] https://twitter.com/trueadm/status/813313438759919616 https://twitter.com/trueadm/status/813313438759919616 [4] https://github.com/orgs/infernojs/people https://github.com/orgs/infernojs/people
- Akkuma 10y agoDominic seems like a truly awesome guy. He also frequents /r/javascript. What I hope is that eventually Inferno can be entirely replaced with React and the teams merged. Right now though the two are similar enough to not stop someone from moving back and forth (especially when Inferno offers a React shim), but are different enough to warrant their own existences.