[Katsunami]

Bwaah. Do you know what I always think about when developing stuff for use on the internet?

Benny Hill & Jackety Sax.

The latest and greatest frontend/backend frameworks from 2014, then trending up and up, are now trending down and down. There are bazillions of frontend, backend, and glue-stuff-together frameworks, all fading in and out of existence. They're hailed as the next big great thing in 2014, and then they're in the graveyard in 2016. If they do still exist, newer versions are often grossly incompatible with older ones.

How is someone to develop a solution on top of that, and then guarantee support and continued development, so a company can depend on said solution for a decade or more?

It's no wonder everything is messed up in IT, and especially on the web. Stuff you learn today is old tomorrow. Everything changes so fast that nothing gets perfected to a point where it can be used for a long time.

How would you like it, if the house you commissioned for building in 2014 starts sagging in 2016, and then got told: "Sorry, those construction techniques are old. They're not used anymore, we can't get new bricks and beams of those kinds. The only thing you can do is use workarounds and hope they'll keep everything standing, or build a new house from scratch."

Right. You wouldn't like it.

I don't mind change. Really, I don't. I can live with it, and I can study new things. I *CAN'T* study new things continuously, however. I also need to *MAKE* shit to be useful, you know.

Even worse, everybody does the same thing differently.

I've often got rejected for jobs because I had been programming in framework X, while the other employer was looking for someone with 3 years of experience in framework Y. No matter that the framework in question didn't even exist three years earlier...