2 ms·
> they aren't the best solution in most cases with what's available now What's available now that superceds them?
by fragmede 3y ago
> they aren't the best solution in most cases with what's available now
What's available now that superceds them?
- __jonas 3y agoWell I suppose that's subjective, I probably put my bias in there but I would say: For mostly static or content driven sites, there are really nice static site generators now. I find Astro[1] really pleasant to use, offering the convenience of SPA framework tooling, while allowing me to build sites that run without the need for any client-side JavaScript but the option to into client-side JS as needed. But also NextJS has a similar static export function, and of course there are many other great SSGs outside the JavaScript world like Hugo. For dynamic web applications like the example from my comment I would just do server side rendering using your language and framework of choice, Phoenix, Rails, Next, Django, whatever. In both cases the issue with 404 routes is avoided. [1] https://astro.build/ https://astro.build/
- shkkmo 3y ago> What's available now that superceds them? The mostly same stuff as before, but slightly better. SPAs were a fad that got very popular, but they were generally a poor solution in most cases and as the fad faded, they stopped being as overused. One of the reasons why SPAs are bad solution is because they interfere with how the web works in significant ways (browser history, caching, server response statuses) and solving those issues without degrading user experience is hard. When a SPA was actually useful, it was worth spending the time to solve those issues. The overuse of SPAs means that most of them did not take the time to solve these issues properly so most SPAs sucked (and still do). This is why I don't understand releasing a SPA server in 2024 that doesn't even try to provide tools to solve those issues.