Stop blaming on JavaScript when all you want is to talk about Front End
Diego ZoracKy
23612

Except that the vast majority of this complexity is coming from backend developers and Node.js JavaScript developers who want the front end to be more like the backend. So instead of learning HTML, CSS, and JavaScript web APIs and being conservative in how they architect web application front ends, they make another framework to circumvent all the stuff they don’t want to have to deal with in their favorite style of programming and run it through a bespoke build process to get something slightly recognizable as a salve to the concerns about the viability of all of this.

Then 3 months later they hop over to a new startup and never have to maintain any of it.

Which is not to say that web front end didn’t have problems before. It needs to change to stay relevant and there were and are gaping holes in it. But I don’t see in most of this a steady or sustainable evolution of a platform that must remain backward compatible, transparent, and approachable to maintain the qualities that propelled it to success. I see a bunch of cargo cultists overengineering in an effort to show off how they could have built a better platform if only someone had asked them when they were toddlers.

And people criticized Flash for all sorts of good reasons. It distracted from real needs and real solutions and was basically an offshoot of the browser wars where a third party vendor tried to hijack all the browsers. ActionScript was great, but proprietary platforms that required technophobic users to install plugins they didn’t understand was never going to work for a number of reasons.

The web succeeded thanks to view source and open standards. Why does everyone seem determined to forget that?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.