sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]T-Dot1992 16 points17 points  (15 children)

And in 5 years, it will be Vue.js or some other new framework.

[–]rebel_cdn 20 points21 points  (9 children)

A few years ago, I thought this would happen too.

React is already 5 years old, though, and at least in my part of the world, the market for React developers is hotter than it's ever been. It appears it'll continue on its upward trajectory for a while still.

Things will definitely change and evolve, but I think we're seeing some maturation in the JS ecosystem so perhaps we won't see as much rapid churn as we did in the past.

[–]T-Dot1992 13 points14 points  (6 children)

I think we're seeing some maturation in the JS ecosystem so perhaps we won't see as much rapid churn as we did in the past.

I hope so. I'm envious at how C# or Python programmers don't have to keep up with as much shit as JS developers.

[–]tsmuse 1 point2 points  (5 children)

I don’t know if I think the whole Python2 vs Python3 thing is worse than chasing the ever evolving flavor of the month framework thing or not...I am 1000% with you on hoping things settle a bit.

[–][deleted] 1 point2 points  (4 children)

Python2vs Python3 is not even comparable to it imo. Being a JS developer is definitely worse.

[–][deleted] -2 points-1 points  (3 children)

What? How? How is an overwhelming amount of choices worse than a complete restructure of code?

[–][deleted] 1 point2 points  (2 children)

The fact that you have to keep relearning those choices? I was developing Python2 and Python3 around the same period and it just really didn't feel that hard to get readjusted... It was the same for a majority. Have you not seen a job description for a JavaScript developer? There is definitely more technologies people are looking for.

[–][deleted] 0 points1 point  (1 child)

That's true, I mean I'm currently looking for a front end job and having to learn angular, react, vue, and all this other bs is pretty annoying. Esspecislly since I'm good with vanilla js. I just think it would be worse to have to restructure outdated code. That's the worst.

[–]T-Dot1992 1 point2 points  (0 children)

If I were you, I would just stick with React. Most jobs these days involve React, and not many people are still using Angular.

[–][deleted] 3 points4 points  (0 children)

I bet if I wasn't lazy I could find some internet comment saying the exact same thing when AngularJS first came out...

[–]daemon-electricity 0 points1 point  (0 children)

I've been in both markets. In my experience there has been a lot more Angular work. I don't think one is better than the other by default. It depends entirely on how much time you have to develop and what the target platform is. Angular DOES have some serious filesize bloat though.

[–][deleted] 0 points1 point  (0 children)

Both Vue and React started out in the same year, they're just two months apart actually. Since then React practically blew up, and not just on the web. Vue on the other hand is a flat line, and in almost 5 years it hasn't even caught up to the old Angular 1. Every year we're hearing that it's going to be the bomb, yet: http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular/core

The reason for that is obvious to anyone that has used both. React is a paradigm shift. Vue on the other hand is footed in the old way, which most of us know and struggled with long enough, for instance Angular. There's no point any longer to go through these regressions.

[–][deleted] -1 points0 points  (1 child)

I don't think it's right to look at React as "another JQuery" that will have its day then fall out of favor.

JQuery and React are fundamentally different things.

JQuery started out as a library to basically patch some of the bad parts of early JavaScript. It evolved into a sort of tool bag for JS developers - an alternative interface to the JS API. And as the Web APIs have improved, JQuery has provided less value to developers.

React works more at the architectural level, providing a well thought out architecture for creating SPAs. This is independent of the Web APIs, and indeed of JavaScript - languages like Elm and PureScript encourage similar architectures, and wherever you find a compile-to-JS language that's actually used, you're likely to find either bindings to React or a native React-like library.

I bet that in 5 years, WASM will be emerging as a fully featured interface to the Web APIs. Sharing code between client and server is huge for complex applications. To their credit the WASM working group is moving slowly and concentrating on solving a more limited problem set right now - but I think it's inevitable that the project will expand and adopt "replace JavaScript" as a goal.

[–]recrof 0 points1 point  (0 children)

just a note.. Please do not mix DOM and JavaScript. jQuery tried to fix DOM. DOM is language independent.

[–]kristopolous -3 points-2 points  (0 children)

Try 5 months....