Earlier quoted context omitted.
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.
Introducing Inferno 1.0
21–27 of 27 posts
Re: Introducing Inferno 1.0
#22Re: Introducing Inferno 1.0
#23Earlier quoted context omitted.
Angular is still around.
Which Angular? Is Angular 2 really the same framework?
Re: Introducing Inferno 1.0
#24As 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
#25Earlier quoted context omitted.
Yes, because in a few months it will be topping the HN headlines on how everyone is porting their applications to it.
I 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.
Re: Introducing Inferno 1.0
#26Earlier quoted context omitted.
Yes, because in a few months it will be topping the HN headlines on how everyone is porting their applications to it.
I 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.
In any case RN isn't something I would ever use, given the choice for writing native applications.
Re: Introducing Inferno 1.0
#27Earlier 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.
I personally think people will start switching to Polymer en masse when Google is done rebuilding YouTube with Polymer.