Live data from Hacker News

Ask HN: Are there any non-SPA front end developers left?

news.ycombinator.com

11–14 of 14 posts

Re: Ask HN: Are there any non-SPA front end developers left?

#11
They never left. But SPA is now more in demand than the old school server-side rendering where you return HTML in your response and let the web browser render it as is.

Decoupling back-end logic from front-end logic has just too much positivise and advantages that doing SSR is just so 2000s. JS brought dynamicity into web page rendering a long time ago. With SPA, or maybe even PWA(who really uses these?), you get also decoupling from the server - a data dynamicity, so to speak.

In short, SPA turns a dumb web page into a dynamic and responsive application that can have the look and feel of a desktop program. Web is no longer static and slow but fast and lively.

Nowadays, static HTML is a niche use case for serving web pages. Like a personal blog or corporate website that is static in nature(information there change sparsely) and can be manually typed or compiled via static website builder, like Hugo.

Re: Ask HN: Are there any non-SPA front end developers left?

#12
If you haven't already, check out the HTMX community [1].

I think there's some recognition that a lot of SPAs didn't need to be SPAs in the first place. At the end of the day, you're just submitting a form for a CRUD app. Good ol' HTML + a sprinkle of JS was enough for most use cases. CSS has evolved to take away some of the stuff that required JS before.

At the moment, I don't think there's really any strong incentives to cut down the complexity of apps by moving away from SPAs. There's real job security in creating complexity. And in some big orgs it's unavoidable. It can change when developers are more aligned with long term outcomes (ex. a product that they own), which usually means smaller projects.

[1] https://htmx.org/

Post reply on HN