71–80 of 123 posts
There is a whole new paradigm in UX design now: get rid of immediate page changes and loading states and instead keep the user on the same page until things load, and show it when it's ready.
Earlier quoted context omitted.
That’s your first problem right there. A diff of that magnitude is too large periodt.
After all years of advancement in computing, and in the year 2025 it's not possible to show a 5000 lines diff anymore.
I suffer it and that’s why I’m building https://githero.app Btw, I worked at GitHub for 3 years and they are very aware that slowness is a big issue throughout the whole product. There was a year long cross team effort to improve things but the main goals were not achieved IMO and it shows.
Earlier quoted context omitted.
Right after Microsoft bought them, github got better, and started implementing long-requested features. (The open letter "dear github" or whatever was that was posted right before the takeover.) This is something more recent.
Yes, remember how copying anything from the code view would also copy the line numbers? It was a relatively small CSS fix, but took years! I never quite understood why this didn't get fixed before by the way, because it really wasn't that hard. Usually when $big_corp takes over $small_outfit things get worse instead of better, due to overbearing $big_corp policy, culture clashes, leadership not really understanding w…
Both the node service and the website
Earlier quoted context omitted.
After all years of advancement in computing, and in the year 2025 it's not possible to show a 5000 lines diff anymore.
I just mean that if you are reviewing over 5k lines of code, it suggests your PR is too big and should have been broken up into smaller changes.
Slower and broken more often, a winning combination!