> Would a site like github benefit much from being a SPA instead of being server side rendered with some JS on the top?
I don't think so. Perhaps there could be some areas they could make the UI richer (say a dynamic code viewer that doesn't require page refreshes, etc)
However, bring it back to the beginning of your comment:
> having heard rails is not a hot thing anymore and SPAs being the new hot stuff
Github doesn't need to be a SPA, nor do most apps. I think many decisions are being made because it's "hot", but generally that's a very poor reason to choose something. (Though to be fair, there's probably many Rails apps that were built in Rails for that very reason)
SPAs carry an entirely new set of concerns. For months, I couldn't order a very important medication online from CVS because their specialty pharmacy site, written in Angular, was busted. I eventually figured out how to make it work by executing Javascript directly in the inspector.
I don't have any feelings myself at all about whether everyone should learn to code, but I'm pretty sure I'm going to remember this anecdote next time someone brings it up.
I don't think so. Perhaps there could be some areas they could make the UI richer (say a dynamic code viewer that doesn't require page refreshes, etc)
However, bring it back to the beginning of your comment:
> having heard rails is not a hot thing anymore and SPAs being the new hot stuff
Github doesn't need to be a SPA, nor do most apps. I think many decisions are being made because it's "hot", but generally that's a very poor reason to choose something. (Though to be fair, there's probably many Rails apps that were built in Rails for that very reason)
SPAs carry an entirely new set of concerns. For months, I couldn't order a very important medication online from CVS because their specialty pharmacy site, written in Angular, was busted. I eventually figured out how to make it work by executing Javascript directly in the inspector.