3 ms·

I feel 2012 PHP is the perfect description for JS reputation today and I've been working in companies where they do node.js as main backend tech since 2011 and

I feel 2012 PHP is the perfect description for JS reputation today and I've been working in companies where they do node.js as main backend tech since 2011 and react since 2015. I think it's the result of a mix of clunky tooling (started with transpiling), OSS maintainers who stopped caring and left a broken mess everywhere and lack of static typing (+ dissatisfaction with TS, despite it being the only sensible option for types), the diffusion of JS in uncool corporate workplaces. I still think both PHP (which I've used extensively between 2006-2011) and JS are fine languages with a few defects.

gjsman-1000 3y ago
I also mean it in the sense of 10 years from now. In 10 years, who is going to want to open up that unmaintained enterprise NodeJS project running on now-ancient Angular or React? Heck, what if it used Vue 2? It’s probably going to be worse than what editing a decade-old PHP project feels like now. That’s if it even builds with just one year of no maintenance. At least the PHP project didn’t rely on packages as simple as leftpad or is-odd.
dep_b 3y ago
Your vanilla PHP will still work in 10 years, with a few deprecation fixes. And since vanilla PHP is such a full-featured language and framework, you don't those third party dependencies.