Was I the only one who saw the title and thought of https://en.wikipedia.org/wiki/Inferno_(operating_system) ?
Absolutely. I was confused by the version number but otherwise happy to see something happening with Inferno. Then the disappointment...
Introducing Inferno 1.0
11–20 of 27 posts
Re: Introducing Inferno 1.0
#12Was I the only one who saw the title and thought of https://en.wikipedia.org/wiki/Inferno_(operating_system) ?
There'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!
Re: Introducing Inferno 1.0
#13Was I the only one who saw the title and thought of https://en.wikipedia.org/wiki/Inferno_(operating_system) ?
Absolutely. I was confused by the version number but otherwise happy to see something happening with Inferno. Then the disappointment...
Thankfully it wasn't about the movie – that certainly was a disappointment!
Re: Introducing Inferno 1.0
#14As a beginner to JS frameworks (and a medium proficiency), is it advisable to skip React and target to learn Inferno instead?
Yes, because in a few months it will be topping the HN headlines on how everyone is porting their applications to it.
Re: Introducing Inferno 1.0
#15As a beginner to JS frameworks (and a medium proficiency), is it advisable to skip React and target to learn Inferno instead?
No, stick with React.
Re: Introducing Inferno 1.0
#16There 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 [2] https://news.ycombinator.com/threads?id=trueadm [3] https://twitter.com/trueadm/status/813313438759919616 [4] https://github.com/orgs/infernojs/people
Re: Introducing Inferno 1.0
#17As a beginner to JS frameworks (and a medium proficiency), is it advisable to skip React and target to learn Inferno instead?
JS Frameworks become obsolete within a year (2 years at most) so you should learn what you like most. The community and documentation available should be a big plus.
Re: Introducing Inferno 1.0
#18As a beginner to JS frameworks (and a medium proficiency), is it advisable to skip React and target to learn Inferno instead?
JS Frameworks become obsolete within a year (2 years at most) so you should learn what you like most. The community and documentation available should be a big plus.
React was first released in 2013 and I don't see it disappearing any time soon.
Re: Introducing Inferno 1.0
#19Earlier quoted context omitted.
JS Frameworks become obsolete within a year (2 years at most) so you should learn what you like most. The community and documentation available should be a big plus.
React was first released in 2013 and I don't see it disappearing any time soon.
In the GP's defense, that's what we thought about Angular two years ago.
Re: Introducing Inferno 1.0
#20There 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…
Dominic 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.