Ask HN: Are there any non-SPA front end developers left?
No synthesized answer yet. Check the discussion below.
Try playing Sverdle with JS disabled! https://sveltekit-template.vercel.app/sverdle
> Unlike the original Wordle, Sverdle runs on the server instead of in the browser, making it impossible to cheat. It uses <form> and cookies to submit data, meaning you can even play with JavaScript disabled!
I know you already called it out but there really is something funny about this. The primary reason I recall for node's popularity is that it means you only have to know one language. I guess that's still true...
Sanity is available immediately if you are willing to be paid less. There are tons of simple, non-SPA, non-stack-on-stack projects out there, they just usually pay 1/10th the complex stuff.
Meanwhile the client is telling me is virtually impossible to find frontend devs willing to write HTML.
Because I don't believe this is a real issue in the marketplace, I will write HTML for your client if they are truly unable to find someone. Writing HTML would be the easiest paid job I could imagine in my field right now.
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.
I don't want to go back to JavaScript for employment so long as its riddled with unnecessary abstraction/dependency nonsense. While I did get tired of solving for the numerous problems that shouldn't exist in the first place I got more tired of insecure peers who were always quick to point fingers. I don't have to worry about that any more.
Rails for example is SSR by default with a bit of js which speeds up the experience with zero dev effort. Anyone starting a greenfield rails project is spa free by default.
I don’t know if that’s still the case.
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.