2 ms·
Wow, didn't know a company this recognizable was still using (and embracing!) Rails. Pretty cool. Also helps explain the fact that they've stuck with a mostly s
by _bxg1 7y ago
Wow, didn't know a company this recognizable was still using (and embracing!) Rails. Pretty cool. Also helps explain the fact that they've stuck with a mostly server-side-rendered app, despite it being a fairly complex tool.
- HatchedLake721 7y agoWhy “still” and “stuck”?
- jaimex2 7y agoignorance
- jrochkind1 7y agoThe perceived performance of Github as I use it as good as any site I use and better than most, so to the extent that's a consideration in client vs server rendered (and it probably should be a big one), it seems to be working.
- jdance 7y agoThe new sites with their own implemented loading bars are just super annoying to use. Sometimes they just stall and look stupid. State is bad! Stateless page loads work! Dont use SPAs unless you do something that looks like a desktop app! Please!
- shantly 7y ago> Also helps explain the fact that they've stuck with a mostly server-side-rendered app, despite it being a fairly complex tool. Probably why it's remained tolerably snappy and light on resources while the "SPA" world so rarely delivers the same.
- _bxg1 7y agoPeople are so sensitive about this. I wasn't suggesting that server-side rendering is bad, only that they're going against a trend. Settle down.