Casually job hunting right now, and it is insane how much React has won to me. Like I knew it was popular, but it seems like it has an outright monopoly with the remaining 5% of market share being split among all the other alternatives.
I don't know what the actual market shares are, but when looking at open positions around the US from coast to coast, it seems to have won.
React is currently in it's honey-moon phase, but many of its warts are starting to show. It probably has another year or two before peaking, but doubtful that such a large heavy-handed library will remain dominant forever.
Also doubtful? What about Java?
Not quite there yet.
Whatever its benefits, Rust remains quite obscure for now.
I'm looking to learn a front-end framework and had a few people recommend Vue. Sounds like maybe I should go for React instead? In case it matters, I'm not looking to be a front-end developer. I'd mainly like to improve some small projects I have. And get the most value out of my time learning a framework.
And we still like Vue a year later. It integrates well with the rest of our site, much of which still has not been rewritten in the functional-reactive style yet. And not having to do a full-on transpile/build step during development is a huge win for reducing cycle times.
I’d use vue if not for svelte, probably.
Svelte's reactivity was also something we had in Splash, the Microsoft-internal UI framework that was used to build the Zune desktop app and Windows Phone 7/8. I haven't enjoyed building UI since then, but with Svelte I can finally enjoy frontend development again.
One thing I don't like about React is that there are so many ways to skin a goat. We write functional components, and while I like them, this instantly makes half of google search results at least slightly irrelevant. However Vue is kind of doing this as well with the Vue 3 syntax change with backwards compatibility.
TL;DR
For resume building + career growth -> learn react
For quick and dirty side project -> use vue
For future proof / bleeding edge understanding -> use webcommponents
If there's one thing I got from these responses, is that I should look at Kubernetes.
Thank you for your answer.
The unfortunate ones that don't manage to move from it will be maintaining 5 year old kubernetes installations.
Kubernetes solves a huge variety of problems with a single platform. In five years, Kubernetes will still be around, but there will be layers built on top of it that simplify common use-cases.
The main problem comes when something breaks and building another abstraction layer on top of it won't help.
I haven’t done much web development in several years myself.
Typescript is mentioned a lot on HN. Saw ReasonML mentioned recently. Vue.js has a movie on the way.
As far as Web frameworks go, what’s popular seems to change every couple years.
The smaller-community frameworks are mostly interesting because they’re not React (i.e. they purposefully target different scopes, niches). The de facto standard framework for component-oriented front end development has been React for a while now. Typescript (which you see mentioned) complements react, it isn’t a component framework that aims to replace it.
K8s has its complexities for sure, but to me it's the simplest - or at least 'only figure it out once' way of running multiple machines (besides having 'the webserver', 'the db server' etc., of course.)
Docker is for building a computer program to run on a single computer.
Kubernetes is for building a cluster, often across many computers with many programs.
They work together.
Rust ranks lower than Delphi on TIOBE, isn't used in a single aerospace, defense, or critical application. Ada has been for almost 40 years, is backward compatible to Ada '83, and has a proof subset (SPARK).
Those waves look more like pond ripples caused by a light breeze.
How about, "Rust - now with bigger pond ripples."
as well as adjust the query for programming-specific engines like GitHub. To have a programming language index not even consider github or stackoverflow as primary sources makes it a laughing stock IMO
Rust is seeing production use in many places and its being accepted more as the sane alternative to C for modern development of high performance software. Ecosystem still not big or mature enough to make big waves, however, but that depends on how you interpret "big waves".
SPAs are used and abused, the tooling to make a performant progressive website with them has gotten better but the know-how is not widespread enough.
React has essentially won the mindshare battle and they are focusing more on functional components. But there are other things with their own healthy niche like Svelte compiling components that manage their own DOM, Elm is still around (and still not 1.0) and it has inspired other "Elmish" frameworks.
Desktop software quality has gone downhill and seemingly everyone is using Electron.
For many companies, Kubernetes is the new normal mode of operation. You should know it, but it's still far from "the way to do things" for industry in general, mostly due to its complexity and learning curve.