Have you started on the Reactocalypse effort yet?
- 2008 to 2012: Jquery
- 2012 to 2014: Backbone
- 2014 to 2016: Angular
- 2016 to present: React
And although there are serious contenders, React still seems like it has a solid lead over all others. If it lasts another couple years, it's been the dominant tool for longer than most.
* Based entirely on "what I was hearing the most about at that time," not on any rigorous methodology. There was still plenty of Jquery code being written last year and there are large, mature codebases out there in Backbone and Angular.
When it comes to large long-historied Angular codebases, I prefer the term "metastasized" over "mature," though now that we're in the 2020s we can almost use "legacy."
That was really a thing I thought, I posted it too and people were like "hmm yes good point."
I know I've been wrong before and since but for whatever reason that one stuck with me as a humbling moment, I had it all backwards.
I’m looking at you -> { blah && }
Talk to a sendmail v8 admin who had to hand edit sendmail.cf rewrite rules.
For examples, here's a comparison implementing the same functionality using React hooks and Svelte: https://github.com/joshnuss/react-hooks-in-svelte
Now, there are ways to handle all this with less code in React as well (for example, MobX), but the current de facto defaults with hooks and Redux create so. much. boilerplate. for. every. little. thing.
I think it's safe to say React wins on ecosystem but loses on verbosity w.r.t Svelte.
Backbone was the first time there was framing at all. So long ago & so not that long ago!
I remember having similar complains in the smaller rails world about a decade ago: every 6-12 months there'd be a new community-favorite gem to accomplish X, where X is any number of common needs: file upload, auth, json serialization, background jobs, etc etc. It was damn frustrating. I had the early-rails equivalent of js framework fatigue! But after a while it quieted down. I wouldn't call it stagnancy and ossification - I'd call it maturity and stabilization. :)
Circa 2005 doing client work during summers off of uni in this newfangled “Ruby on Rails” (v0.8.x). I was new to all of it. Coming from Flash/Flex/AS and jumping both feet into Ruby, Rails, JS via Script.aculo.us! Great times!
:shudder:
(I did make a bunch of money with that one project that went live for about 8 days before the company we did it for sold out and the new owners shut it down immediately. _So_ glad I was never on the hook for production support on that...)