[coldtea]

>Sounds like the typical pretentious, the world is changing and I don't like it. Take the time to learn new technologies and adapt to changing landscapes.

Why? Most of the times is fad. Learning some select things well is way better (and more feature proof) than "learning new technologies and adapting to changing landscapes" (e.g. VB in the nineties, Java/C# later, Rails after that, Node now). One could have been a stable salaried top-end engineer in the same, non-shifting, niche the whole time...

[tracker1]

JSX and Redux are going nowhere... they'll probably outlive React, though I also think that's going nowhere anytime soon.

Redux (and similar single unidirectional stores) is a paradigm shift, but seeing ever broadening adoption and similar ngrx/store for example in the angular side.

JSX as a compositional representation of a component tree is just plain useful... it's your component markup in your code, instead of code here, style there, markup over there... it's all on concern, the component. Many newer frameworks that differ from React on some technical reasons are using or suggest JSX transforms.

You get that in a more stable platform with React. Add in fetch, react-icons and material-ui you're pretty close to set... start with create-react-app and your off and running, not much, if at all harder than getting angular1 up.

And while Node is no longer growing exponentially, it's still one of the most prolific open communities around (including npm for client-side JS projects).

As to your list.. Java and C# are pretty firmly around today.

[coldtea]

>JSX and Redux are going nowhere... they'll probably outlive React, though I also think that's going nowhere anytime soon.

Let's check back in 10 years.

>Redux (and similar single unidirectional stores) is a paradigm shift, but seeing ever broadening adoption and similar ngrx/store for example in the angular side.

And in a few years we could have another paradigm shift, with webassembly bringing about e.g. a nicer UI stack for web work.

>As to your list.. Java and C# are pretty firmly around today.

Speaking of Java, that I've followed best, where are Applets? Or J2EE? Or Swing? Or JS Faces? Or that java grid API that would revolutionize computing? Or lots of other Java-related fads du jour that history forgotten, but at the time had loads of adoption and were touted as the best thing since sliced bread?

[tracker1]

Not sure, the only things I've dug deeply into are Netscape Livewire (server javascript), Classic ASP (JScript and VBScript), PHP, ASP.Net, Ruby on Rails, Castle Monorail, ASP.Net MVC, Node (express, koa), Backbone, MEAN-stack, React .. some interest in go, rust and .Net Core lately.

Of all the above, React is the first paradigm (combined with a Node backend) that EVER felt like the right way to do things... all others were "Cool", then dig in and get really disappointed somewhere. The more I've gotten into React... (I didn't like a lot of the early flux-like frameworks, but enjoying Redux) the more I feel it's really close to the right way to build web applications.

Of the above, I really disliked PHP and didn't like RoR too much, mostly because I don't care for ORMs at all really, even Entity Framework irks me at times, but at least it's easier to manage than others I've worked with. I've done one-off things with other tools/frameworks, but none really felt right... And this is in two decades of web applications development.

Mongo and RethinkDB feel close to right similarly. Postgres + plv8 feels really close too, but for the clustering.

For now, Web Assembly can't touch the DOM. And I'm only guessing, but it's likely the first implementations that bridge the gap will be around React/JSX or a similar core for the communication, and representation of UI vdom. Soemthing using the `material-ui` package could be awesome.

[nkkollaw]

What about Polymer and web components?

I think that's the future, not React.

[tracker1]

Web components, or something like it may well be the future... But to me the web component structure feels more alien than React.. it's almost the inverse though. Of course, that's once the browsers better support it, and ES6 modules natively is probably the biggest adjacent need, that will be some painful times during the transition.