Comment by koakuma-chan

4 days ago

If you have front-end and back-end separate, you're doing web development wrong.

Can we post a single phrase as a HN article? This is one of the main problems with web development nowadays, nobody gets this right... to the point that it's popular to criticize a company trying to hire a single person for both holes as "cheapening out".

Also, this is a really obvious thing. It's unbelievable how the main way people organize is the other way around.

But what if it isn't just a basic website? Most sites I've worked on required things like content management, or auditing stuff, a bunch database stuff, SAML single sign on etc.

Most languages end up being better at some parts of the stack, like Java for overcomplicated enterprise BS backends. It seems bad to "fight" that trend.

  • A full stack framework like Next.js is, at the end of the day, still a server running on Node.js, so there is nothing that prevents you from doing anything that you could be doing with a regular express.js server. Is there anything that prevents you from implementing content management, auditing stuff, or database stuff in your Next.js project? Nothing comes to my mind.

Totally agree. I've been using blazor server + Claude for project and it just removes all the stupid complexity of having react + a rest API.

  • I know right? You can share types, you don't need to glue API, etc etc. Why don't people realize that.

    • People do realize that, which is why such frameworks have first appeared decades ago. It's just that you can't fully paper over the network gap and pretend that it doesn't exist; eventually, the abstraction leaks.

      4 replies →