Hacker News new | ask | show | jobs
by bphogan 3892 days ago
No, I see this everywhere.

There's a large segment of the software industry that believes their way is right, and everything else is wrong. The phone you use, the computer you use, etc.

Recently I had someone tell me that if you're still writing apps that serve HTML, you're "doing it wrong" because everything should be an AJAX backend with JavaScript. Is that the way apps are going? Certainly. But is that the way to do everything? No.

I did a conference talk on Elixir this last week, and later ran into someone who told me that there's no need for that as he can do everything better and faster with Node, and "why should I waste my time learning THAT? I saw a benchmark showing that Node was faster, so I'll use that."

Here's what I think the problem is. Every morning you log on to Twitter and HN and you see ten new things out there. You don't know when your thing of choice will be out of style with the clique you run with. And it's tiring. So developers are so insecure about their own knowledge that they seem to seek out confirmation bias, surrounding themselves with an echo chamber that believes what they believe. That's more comfortable. And anyone who believes differently has no business being there.

It's like high school, really.

1 comments

> Recently I had someone tell me that if you're still writing apps that serve HTML, you're "doing it wrong" because everything should be an AJAX backend with JavaScript. Is that the way apps are going? Certainly. But is that the way to do everything? No.

Excuse me, but what are the advantages of not serving HTML directly? I honestly find that way more convenient (possibility to give links for example).

Main one is that you deliver less content if you serve JSON instead of HTTP.

Pros: You don't have to rebuild a full HTML page for every new query, be it server-side of client-side, you don't have to serve assets for every request and client doesn't have to recall/reinterpret them, less content means it's served faster,...

Cons: More strain is put on the client (virtual DOM, keeping the front-end framework in memory). Though it's negligible on most clients.