3 ms·
They didn't leave the architecture alone, right? They shoved React in and created a weird SSR + React frankenstein that is objectively worse in many ways.
by sosodev 1mo ago
They didn't leave the architecture alone, right? They shoved React in and created a weird SSR + React frankenstein that is objectively worse in many ways.
- esperent 1mo agoReact apps with SSR is standard these days.
- sosodev 1mo agoSSR that is javascript native, sure. This is still Ruby doing the rendering.
- esperent 1mo agoWhat's the difference? If it's SSR it's happening on the server, the only benefit of using JS is ergonomics. Ruby is fine otherwise.
- sosodev 1mo agoRuby can't render React code. JavaScript can. With GitHub it seems that they sometimes can do SSR for the React bits, but that must mean that they're invoking a JavaScript interpreter within the Ruby process. Which means they have the overhead of two runtimes and the jank that comes with the IPC between the two. It's just pointless hacks on hacks. GitHub didn't need React on the frontend and any potential resource savings of client side rendering were lost when they realized they need to do SSR on that stuff too. I've encountered so much frontend jank as they expanded that portion of the stack whereas it was always excellent when it was just Ruby SSR and minimal JS on the frontend.
- Zanfa 1mo agoWish they spent some AI tokens on that abomination to fix at least some of the countless issues it has, because their human engineers definitely won’t.
- phailhaus 1mo agoAnd yet, the React/SSR infra has never gone down.
- tom1337 1mo agoWell, maybe not completely down but the amount of navigation issues, screen flickers and unhydrated stylesheets I have everyday is not something I'd expect from such a product.