I think the unusual thing is that it was written in a week. I highly doubt that they read and understood all 1M lines. But if it works and people use it, what does that mean for software? Should we still care about the code that’s written? Should we even look? I’ve always thought so, but maybe I’m just biased.
Nothing is keeping them to this plan other though, I hope they do follow through. That would make the graph on the page misleading in the other direction though as the speed feature would be included in the non plus version.
I want to also say I'm a happy vite user (and the other projects that team makes).
Ehhhhh... what does this mean for the open source versions of all these libs? You could interpret some of the graphs as vite oss isn't getting rolldown. That would be disappointing but still okay.
Agreed, I really liked how the site looked. I thought it was really slick and I am blown away by the how easy the author added extra information in a blog post. Nice work!
I looked a bit into the JavaScript loaded when going to GitHub and my best guess as to what it’s using react for is the copilot chat.
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.