> because those kinds of features requires the back end to execute Git implementation code which can invoke some pretty expensive cases
Github has the blame view of files, which is much more expensive.
Re:Why SQLite does not use Git (2018)
by tapan_jk on Saturday November 06, 2021 @12:18AM
(#29127485)
An ex colleague uses GitHub Enterprise at work, and he reports running into some issues that are never seen on GitHub proper. Most notably, network view of repos and GitHub pages experience extended downtime. Wonder how GitHub manages the uptime of these features for millions of repos because I never see these fail there.
Re:Why SQLite does not use Git (2018)
by clhodapp on Saturday November 06, 2021 @05:36AM
(#29128785)
I will note that some features actually don't seem to scale reliably on GitHub proper. For example, the profile pages of prodigious commiters tend to time out on. As an example of one that pretty much always does it, check out https://github.com/scala-steward (not on mobile).
> why it seems Github goes out of its way to hide the typical commit tree navigation
Wild guess: because those kinds of features requires the back end to execute Git implementation code which can invoke some pretty expensive cases. Imagine that across thousands and thousands of repositories being accessed at once.
They want to steer the user toward doing a clone and doing their own in-depth drilling on the copy.
CGIT caches for better performance; but caches require extra storage and some sure-fire expiry mechanism so it doesn't grow and grow. Caching things for internet rando visitors doesn't seem like a good idea.