Hacker News Reader

Comment by erhaetherth | Hacker News Reader

There's 2 types of web pages. Websites and web apps. If you're building a web app, you're going to want a framework that isn't going to fall apart the second things start getting complicated. If you're making a little marketing website, sure, sprinkle some jQuery on there and call it a day. Probably better for performance and SEO unless you want to spend 10x as long micro-optimizing your SSR. Point is, there's different use-cases.

View on HN

It’s all the same. The difference is not in the product but in the developer’s perception of the product. The code and the user don’t notice the difference, just the developer in the middle. There are those who can dynamically put text on screen and those who need just a little help to dynamically put text on screen.

> the user don’t notice the difference

Users do notice the difference is large JS framework driven applications.

Yeah, they notice how slow and janky they are, and how often they're staring at empty gray boxes while things load.

Okay, what part of what I said are you trying to refute or educate me on?

There's a large proportion of posters on HN who spend their days building web apps. They are very likely to stick to using what they know, even when building web sites.

If you spend your days working as a welder, and suddenly need to build a box for some reason, you're probably not going to be breaking out the fine wood joinery tools. You're probably going to take some sheet steel and weld up a box and move on to whatever else you have to do.

It's not a problem, it's not a fault, it just how things are.

> Okay, what part of what I said are you trying to refute or educate me on?

Not the GP, but that's why, when applicable, I try to prefix my replies with a variant of "I agree, and btw..."

Reply on news.ycombinator.com