In the 1990’s, a common language used to teach Computer Science was Pascal. It was easy to understand, and so it taught people how to program.
In the 2000s, Java replaced Pascal for that job, and until today, it’s mostly still the case. That’s at the college level.
Will React be here to stay? Yes, like everything in tech, it will stick around.
And React will go out of style too.
It’s hard to take React too seriously when you look at the long term. There’s certainly a lot of frenetic energy around each of its releases, around all the ready-made components you can freely use, around how it can be used to build mobile apps and how it promises new developers that it’s the only thing they need to know.
But the enthusiasm seems suspect. Its main sponsor, Facebook, is a company whose morality is on trial. The dependency on any one company for a framework’s livelihood is something to worry about, much more when depending on a company like Facebook.
They say React is not a framework, that it’s just a library, but real-world installations treat it like an all-encompassing baseline, from the front to the back. jQuery was a library, React is not just a library. They say React’s beauty lies in that it’s just overseeing the view. In reality, you end up managing the state (the local data structure affecting the view), since the only way the view won’t break is if the state never breaks.
Who knows? Maybe there’s going to be another thing after React. And maybe you’ll be the one who will be inventing it.
Credits to Jean-Claude Batista for the Overreact title idea.