In like 2009 or something, someone, somewhere, building software on the Internet, took a step back and thought to themselves:
Which is a valid complaint. A lot of data science geeks write As Much Python as Possible, and some enterprisey systems engineers write As Much Java as Possible, and some people who work deep down in the mines right up next to the bare metal write As Much C As Possible, and God bless them.
I know what you're thinking
create-react-app is beyond fathoming. No doubt.
But the seminal JS fatigue article was written in 2016 so writing about this in 2021 is Old Hat in a major way.
What I'm really here to figure out
In fact, as far as JS goes, most of them just want React (and Typescript if they're feeling adventurous). Which is fair: component-based UI builders really are the nicest to use, and 2-way data binding with state makes lots of basic stuff really easy. And the ecosystem around React means that smarter people than you have already solved like 98% of the problems you'll face outside of the labs at Google and Facebook and Stripe.
But the rest use some other stack on the "backend". A much higher number than I would have thought are looking for something that runs on the JVM—plain ol' Java, more often than not. If the company is forward-looking and scale-oriented, they might also ask for Go.
So what do the big shakers at the top of the tech pyramid know that I don't?
What I got up to in February 2021.
What I want for the blog; thoughts on template builders; Cassie Evans on SVG animations; Supabase.