4 ms·

Why does this always come up? Maybe the author does need the SPA. This comment does not seem particularly relevant to the contents of the article.

_xnmw 5y ago
CORS is just one more problem from the class of performance problems that only SPAs have. Seems very relevant to me.
- rattlesnakedave 5y ago
  > only SPAs have That’s a bold claim.
lostcolony 5y ago
Because if you're re-examining your need of CORS and evaluating whether it makes sense to instead host everything from the same host, you can also re-examine your need of an SPA and evaluate whether it makes sense to instead just render everything server side; it'll solve even more problems if you can.
- rattlesnakedave 5y ago
  > it'll solve even more problems Wow. Why doesn’t everyone do this?
  - _xnmw 5y ago
    Actually, a lot of people do. Ever heard of Laravel, Django or Ruby or Rails? Outside of the React/JS world, a lot of developers are happy solving real business problems instead of working with hacks that were built on top of browser DOMs.
    - rattlesnakedave 5y ago
      That’s great to hear. Hopefully I can grow up to be one of them some day.
    - lostcolony 5y ago
      I mean, to be a bit more charitable, when you have use cases that require server pushes, the traditional server rendered pages don't work so well, and that is where SPAs make sense. Mind you, a lot of the frameworks for rendering server side have started to include natural ways of handling those updates (Phoenix Liveview for instance being one I'm familiar with), that makes it so you likely don't need an SPA in those situations, but there are still use cases where an SPA may be simpler or may enable a UX that otherwise would not be possible. But to the apparently snide response to my original comment, while there may be reasons for SPAs, there are also plenty of uses of them that could be more simply done via server side rendering, especially with the place such frameworks have moved towards, in enabling server pushed updates.
  - Nextgrid 5y ago
    Some people's careers are based on JS frameworks and managing (or perpetuating) frontend complexity. How many will voluntarily put themselves out of a job?

_xnmw 5y ago

CORS is just one more problem from the class of performance problems that only SPAs have. Seems very relevant to me.

rattlesnakedave 5y ago
> only SPAs have That’s a bold claim.

lostcolony 5y ago

Because if you're re-examining your need of CORS and evaluating whether it makes sense to instead host everything from the same host, you can also re-examine your need of an SPA and evaluate whether it makes sense to instead just render everything server side; it'll solve even more problems if you can.

rattlesnakedave 5y ago
> it'll solve even more problems Wow. Why doesn’t everyone do this?
- _xnmw 5y ago
  Actually, a lot of people do. Ever heard of Laravel, Django or Ruby or Rails? Outside of the React/JS world, a lot of developers are happy solving real business problems instead of working with hacks that were built on top of browser DOMs.
  - rattlesnakedave 5y ago
    That’s great to hear. Hopefully I can grow up to be one of them some day.
  - lostcolony 5y ago
    I mean, to be a bit more charitable, when you have use cases that require server pushes, the traditional server rendered pages don't work so well, and that is where SPAs make sense. Mind you, a lot of the frameworks for rendering server side have started to include natural ways of handling those updates (Phoenix Liveview for instance being one I'm familiar with), that makes it so you likely don't need an SPA in those situations, but there are still use cases where an SPA may be simpler or may enable a UX that otherwise would not be possible. But to the apparently snide response to my original comment, while there may be reasons for SPAs, there are also plenty of uses of them that could be more simply done via server side rendering, especially with the place such frameworks have moved towards, in enabling server pushed updates.
- Nextgrid 5y ago
  Some people's careers are based on JS frameworks and managing (or perpetuating) frontend complexity. How many will voluntarily put themselves out of a job?