4 ms·
Ugh, they've gotten rid of the commit message, because they merged "commits" "branches" "tags" into the header bar. If you want to see what the latest commit wa
by misnome 6y ago
Ugh, they've gotten rid of the commit message, because they merged "commits" "branches" "tags" into the header bar. If you want to see what the latest commit was you need an additional click.
Turns out that glancing at the header was useful to tell what was going on!
On the plus side, GitLab's repo view (which I disliked because it felt cluttered and always hard to find what I wanted) is now easier to use and read than GitHub's, so that makes changing easier.
- misnome 6y agoAlso, I'm noticing a lot more "preload" pages ... e.g. the page loads with blank placeholder fields for the commit and text information that's then replaced live after loading the page. Maybe it did this before and is just slower now?
- verdverm 6y agoyup, this is a Jira move, GitHub sounds like it's on it's way down fast
- misnome 6y agoMy cynical guess is that they used “page load time” as a metric to prove their new system was “faster”. And maybe only tested internally on a faster system, or with hot-cache repository loads? It doesn’t seem to do it on reloads, though going away for a bit and coming back seems to cause it again (and, visibly, different parts of the page load at different times). Anyway, It definitely reeks of “enterprise” so I guess Microsoft finally got enough people into github to steer the ship towards the iceberg.
- verdverm 6y ago> reeks of “enterprise” you made my day! thanks