Live data from Hacker News

Why is modern web development so complicated?

vrk.dev

51–60 of 731 posts

Re: Why is modern web development so complicated?

#51
Because, Webpages have become complicated. Suddenly, you have all this interactivity going on, which you didn't have a decade ago. We went from a series of simple hyperlinked inter-connected webpages to all these popups shoving onto our face, useless fake computer bots pretending to be tech-support and finally big co. tracking every single click, every pixel of your mouse movement. The web has come a long way to support all these.

One of my clients was an airline. He asked if we could track the usage stats of his in-flight entertainment system (just stats, no PII). I thought about it and said yes. Even I was amazed I said because a decade ago it wouldn't be possible. I got it done with service workers (because flight wi-fi isn't a 100% always on connection).

It was a boon for me because I made a lot of money on that project and I needed the money. It's also a curse because every browser has all these invisible code running behind the scenes whether you want it to or not.

I miss those days where everything was just a bunch of tables and default system font-powered webpages with plain blue links. No CSS, no popups, just html and pure content.

Re: Why is modern web development so complicated?

#52
post #42
post #2

I don't know, but I do know I would rather fix a race condition on a multithreaded application than figure out how flexbox works or even understand all the different parts of the DOM.

Might that be simply because you are more interested in the one thing than the other? I can't come up with any objective measure of complexity that could show flexbox as being more complex than multithreading.

A large part is definitely because I get overwhelmed and have trouble ignoring the "magic" that the article talks about.

Re: Why is modern web development so complicated?

#53

I think the default should be: Don't use any JavaScript if you don't have to. And if you have to, use it responsibly. Recommended reading: - "Responsible JavaScript: Part I" by Jeremy Wagner ( https://alistapart.com/article/responsible-javascript-part-1... ) - "A JavaScript-Free Frontend" by Matt Reyer ( https://dev.to/winduptoy/a-javascript-free-frontend-2d3e ) Disclaimer: I'm from Germany, but have a 6-y/o Android…

javascript rules, and you can't build truly interactive sites without it (try to build a refine-as-you-type search bar with just html and css).

Here's my hot take: JS is good and has made the web better.

Re: Why is modern web development so complicated?

#54
post #34
post #2

I don't know, but I do know I would rather fix a race condition on a multithreaded application than figure out how flexbox works or even understand all the different parts of the DOM.

I don't know, but I would rather weld steel together in a sky scraper than figure out how to hang cabinets or even understand all the different types of crown molding. I always think the backend versus front end statements are hilarious when cast to other activites. They always carry a tone of derision while completely missing the point that they are different problem spaces and skill sets.

Also, {french cleats,flexbox} are awesome for {hanging stuff, sane and responsive page layout} and really pretty simple.

[1] https://en.wikipedia.org/wiki/French_cleat

Re: Why is modern web development so complicated?

#55

It doesn't have to be complicated, if you get support from above. A few weeks ago I launched a new web site for a health care company. HTML, PHP, CSS, and MySQL. No frameworks. No javascript. No garbage. It replaced a site that was a mess of javascript libraries on top of frameworks on top of a half dozen jquery version and on and on and on. The company administrators, doctors, practitioners, etc... are so happy with…

You don't even use a backend rendering framework?

MVC PHP frameworks are very nice and they don't move as fast as those javascript frontend rendering.

Also the ORM deals with any security problems and most framework deals with other security deals too including session handling.

Re: Why is modern web development so complicated?

#56
It's not the tools, it's the 'Full Stack' title. If you want to be a 10x employee, be a full stack architect you need to know all of it.

You simply cannot be a monolithic craftsman, who wields only a few tools well. Because if you do that, in 10 years you'll be left in the dust complaining about ageism vs knowing new tooling

I'm not advocating this is a good thing, but its the environment we have fostered for ourselves and now we don't like it.

Re: Why is modern web development so complicated?

#57
In 2012 you were building sites and even applications with a stagnant language (JavaScript) that lacked any module/bundling support while having to support multiple browsers with differing standards. Routing, state management, dependency resolution, etc. were handled on an ad hoc basis if at all.

The current complexity is a result of addressing these issues and doing so at a rapid pace.

Re: Why is modern web development so complicated?

#58
Because a Web developer had $PROBLEMS problems, and he thought, "I know! I'll add an abstraction layer!" Now he, and the world, had $PROBLEMS + 1 problems. Repeat ad nauseam since the mid 90s.

Also, an application software vendor had A(m,n) problems and thought "What we need is to make the Web into a universal platform capable of supporting any application." Now they, and the world, had A(m+1, n+1) problems.

Re: Why is modern web development so complicated?

#59

It doesn't have to be complicated, if you get support from above. A few weeks ago I launched a new web site for a health care company. HTML, PHP, CSS, and MySQL. No frameworks. No javascript. No garbage. It replaced a site that was a mess of javascript libraries on top of frameworks on top of a half dozen jquery version and on and on and on. The company administrators, doctors, practitioners, etc... are so happy with…

Did you consider that the next developer might well come along and post a similar comment:

> It replaced a site that was pretty much a home-grown PHP framework written by a single developer. Random mixed logic in templates, hard to update CSS and a poorly designed 'not-an-ORM' ORM.

Not to say that your rewrite is like that, but one man's garbage is another man's treasure.

Post reply on HN