3 ms·
I’ve always assumed it went something like: the web became popular, lots of programmers from other fields moved to web programming since that is where the jobs
by irrational 5y ago
I’ve always assumed it went something like: the web became popular, lots of programmers from other fields moved to web programming since that is where the jobs were at, they brought with them all their cruft and complexity and forced them onto web development (regardless of whether it was appropriate or not), and thus we have the insane complex mess web development has become.
- soperj 5y agoI honestly think it's been the other way around. UI/UX has forced this mess. People wanting it to feel real time, even though it isn't.
- bobthepanda 5y agoI would go a level higher and say it is the commercial nature of the web today. The web ceased being only about hypertext documents in the strictest sense a long time ago, and what makes money and attracts consumers seems to be "app-like" experiences and not basic hyperlinked forums or web portals. And their ability to make money only creates more of them.
- bobthepanda 5y agothere's a couple of things at play * JS's history is all about "quick and dirty". jQuery in older times was meant to paper over the quick and dirty and give developers more convenience, and old JS without JQuery was pretty awful * we are asking JS to do things it was never meant to do; in particular, the desire for "app-like" experiences and SPAs. * JS is very backward compatible, which means old webpages can be archived, but also means that all the warts are still around. * JS interpretation depends on browsers, which means if you want to use some modern features you will have to use some kind of transpiling, polyfill, and or framework to get some consistent behavior on all of them (jQuery in older times, babel today), and the differences in browsers means that these adapters have to be mind-bogglingly complex a lot of times