That's a fair complaints. However, it's clearly a design decision, whereas the author is trying to imply that it's gotten generally worse because they switched to using a frontend framework.
https://github.blog/engineering/architecture-optimization/ho...
That said, most (not all) of it still works with Javascript disabled
It’s still using turbo rails and doing full ssr reloads. Something very at odds with react router which it’s also loading.
It’s still loading catalyst (their homebrew web component lib) which from what I understand doesn’t seem to offer react bindings. It even loads lit (another web component lib), which I couldn’t find the react bindings for.
If it’s just for the copilot chat I’d still say GitHub is mainly rails based though would love to hear if anyone has any more / better insight.
Not that it is particularly difficult with Vanilla JS etc. but maybe slow enough you think, hey why are we doing this?
React it's 5 seconds to do, you are done so quick with the actual code you might not consider the implications.