3 ms·
I still think separating frontend from backend makes life easier even though frontend has been chaotic for a decade, and it shows no sign to slow down
by synergy20 4y ago
I still think separating frontend from backend makes life easier even though frontend has been chaotic for a decade, and it shows no sign to slow down
- oblak 4y agoDepends on what you're doing. There is great value in SSR but how does one even make anything dynamic/interactive without JS? You can't, so you start adding pure non-spa tainted js. Then you add features until your amazing purist solution is an unworkable mess stuck in the mid 2010s.
- omnimus 4y agoThis is just problem of structure. I am not convinced that there is particularly higher chance to end up with "unworkable mess" with SSR compared SPAs (of course most projects end up being a mess). If you look at the hottest trend of the "island architecture". New frameworks like Astro (https://astro.build/ https://astro.build/) and Fresh (https://fresh.deno.dev/ https://fresh.deno.dev/). They are basically what are you describing. All SSR but with dynamic parts. Seems like these "islands" by their nature are less entangled than full SPA.
- pron 4y agoSeparating the frontend from the backend doesn't necessarily mean putting all of the frontend logic in the client. Your server can also have separate frontend (or "view") logic.