Live data from Hacker News

The GitHub website is slow on Safari

github.com

191–200 of 367 posts

Re: The GitHub website is slow on Safari

#191
post #33
post #19

Can someone who's worked in an org this large help me understand how this happens? They surely do testing against major browsers and saw the performance issues before releasing. Is there really someone who gave the green light?

The way it works in tech today is that there are three groups: - Project managers putting constant pressure on developers to deliver as fast as possible. It doesn't even matter if velocity will be lost in the future, or if the company might lose customers, or even if it breaks the law. - Developers pushing back on things that can backfire and burning political capital and causing constant burnout. And when things DO…

This is shockingly accurate - are you a Hubber? :)

Re: The GitHub website is slow on Safari

#192

The Github website is slow everywhere. It is truly a piece of shit software both in terms of performance but also UX/UI and everything in between. It's a product of many cooks and their brilliant ideas and KPIs, a social network for devs and code being the most "brilliant" of them all. For day to day dev operations is something so mediocre even Gitlab looks like the golden standard compared to Github. And no, the pro…

"The Github website is slow everywhere." Perhaps it depends what software one is using For example, commandline search and tarball/zipball retrieval from the website, e.g., github.com, raw.githubusercontent.com and codeload.github.com, are not slow for me, certainly not any slower than Gitlab I do not use a browser nor do I use the git software

The website is fast if you don't use the website

Re: The GitHub website is slow on Safari

#194
post #121

Earlier quoted context omitted.

Oh, certainly, didn't mean that you had to avoid using your IDE to autorename a variable yourself (to avoid the boolean issue) and diffed results to those of the PR Or that you had to avoid Ctrl+F "CustomerEmail" and see whether you had 1000 matches that matches the number of changed files or only 999 due to some typo. Or using the web interface to filter by file type to batch your reviews. Or... Just that in none of…

I envy your IDE being able to do a rename of that scale. I work in a large C++ codebase and a rename like that will actually just crash my vscode instance straight-up. (There are good automated tools that make it straightforward to script up a repository-wide mutation like this however. But they still generate PRs that require human review; in the case of the one I used, it'd break the PR up into tranches of 50-ish f…

Yeah VSCode is pretty terrible at refactorings that Jetbrains or Zed will do basically instantly.

Re: The GitHub website is slow on Safari

#196
post #124

The Github website is slow everywhere. It is truly a piece of shit software both in terms of performance but also UX/UI and everything in between. It's a product of many cooks and their brilliant ideas and KPIs, a social network for devs and code being the most "brilliant" of them all. For day to day dev operations is something so mediocre even Gitlab looks like the golden standard compared to Github. And no, the pro…

It's frustrating, because GitHub used to perform quite well, before it was a single page app.

Github's Primer design system was wonderful when it was a pure CSS system that could be used with any framework. Sadly, M$ killed that and made the new Primer design system shitty-React consumption only.

Re: The GitHub website is slow on Safari

#197
post #62

Earlier quoted context omitted.

exactly. I don't want to do a "no true scotsman" to defend React, but circumstantial evidence suggests that they wildly misused the tool

So PHP <6 was a great language?

The front-end is usually just a thin layer on top of a database, sometimes with backend services (queues/processing). Having a bad language on the front-end actually helped. You don't want to write code because of the bad language, you write less code, less code is less bugs. You had to be invested to increase the lines of code. It's like the hard chair of programming languages. If you don't want programmers to dwell there, bring the hard chairs.

Re: The GitHub website is slow on Safari

#198
post #33
post #19

Can someone who's worked in an org this large help me understand how this happens? They surely do testing against major browsers and saw the performance issues before releasing. Is there really someone who gave the green light?

The way it works in tech today is that there are three groups: - Project managers putting constant pressure on developers to deliver as fast as possible. It doesn't even matter if velocity will be lost in the future, or if the company might lose customers, or even if it breaks the law. - Developers pushing back on things that can backfire and burning political capital and causing constant burnout. And when things DO…

Exactly this.

Re: The GitHub website is slow on Safari

#200

GitHub web used to be great. Then some charlatan thought to embrace the React hype and it became terrible to say the least.

As a hater of React, I don’t think React itself is to blame.

Old GitHub was very light on features, whereas the new UIs are way more curated on the surface.

Unfortunately all of this brings in tons of complexity. It doesn't help that there are a lot of junior developers working on it, clearly.

Post reply on HN