Re:JavaScript broke the web (and called it progress)
by nchmy on Saturday June 21, 2025 @10:10AM
(#44337743)
Would it be a good thing if a million unemployed devs were employed to just dig a big hole? Or, worse, cut down forests with axes?
Job creation for the sake of it isn't a good thing. What matters is whether it creates actual value, and does so efficiently.
The thrust of this, and many similar articles, is that it JS frameworks were largely a very inefficient, ineffective solution to a nonexistent problem.
The fact that they're ALL now SSR-first - without the robust and comprehensive functionality of longstanding ssr frameworks, cms etc - proves this.
Job creation for the sake of it isn't a good thing. What matters is whether it creates actual value, and does so efficiently.
The thrust of this, and many similar articles, is that it JS frameworks were largely a very inefficient, ineffective solution to a nonexistent problem.
The fact that they're ALL now SSR-first - without the robust and comprehensive functionality of longstanding ssr frameworks, cms etc - proves this.