4 ms·
GitHub used to be great when the frontend too was in ruby, the react rework might've got somebody promoted but performance was never the same. GitHub is so dat
by epolanski 5mo ago
GitHub used to be great when the frontend too was in ruby, the react rework might've got somebody promoted but performance was never the same.
GitHub is so data heavy and there's so little reactivity that it should really be server side rendered.
- IshKebab 5mo agoThe frontend was Ruby?? Are you sure?
- pdpi 5mo agoAs in rendered server-side.
- ClikeX 5mo agoNot literally. And I would hardly say it was a matter of language superiority. I love Ruby myself. But Github was a lot simpler when it was still just a Rails app. But Rails was SSR by default, and most of the frontend was just Embedded Ruby (ERB) template files all over the place. And way back when, it was even relatively common to use Javascript supersets like CoffeeScript[1] and Opal[2]. The latter being Ruby that compiled to JS. [1]: https://coffeescript.org/ https://coffeescript.org/ [2]: https://opalrb.com/ https://opalrb.com/
- TeriyakiBomb 5mo agoYes, standard rails. Rails does not ship with components out of the box and the most prominent component system for rails was built and is maintained by GitHub. They have been moving to React for the last few years though, it seems to be more about hiring and ergonomics rather than capability.