Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The GitHub website is slow on Safari

github.com

Post reply on HN
Print view View original

211–220 of 367 posts

Re: The GitHub website is slow on Safari

#211

Post by [deleted] »

shadowgovt wrote: post #112
ballenf wrote: 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?

I've had some experience with Google here. The short answer is: no, they don't. Google Cloud relied upon some Googlers happening to be Firefox users. We definitely didn't have a "machine farm" of computers running relevant OS and browser versions to test the UI against (that exists in Google for some teams and some projects, but it's not an "every project must have one" kind of resource). When a major performance reg…

[deleted]

Re: The GitHub website is slow on Safari

#212

Post by treve »

dham wrote: post #115

Everything is slower across every single facet of computing. Something is happening. I have a brand new Mac Studio M4 Max with 64gb of ram and every site is still slower than it was on a 2011 Mac Book Pro.

Web developers should be forced to use hardware that's roughly at the 10th percentile in performance of their user base, not the 90th. Alternatively, make performance a WCAG concern.

Re: The GitHub website is slow on Safari

#213

Post by kccqzy »

arresin wrote: post #209
kccqzy wrote: post #120

Earlier quoted context omitted.

React was not a bad idea. SPA's tend to be a bad idea. React is just a tool to make SPA's easier to write.

React is a terrible idea. Everything about it is garbage. The api. State. How they do rendering. The “vdom”. It’s unnecessarily complicated and Byzantine. Like it was designed by someone trying to bill a large company many hours. Svelte is ok. It could have been great but the api for their version of observables is a disaster (which I hope they eventually fix). Sveltekit is half baked and convoluted and I strongly ad…

React is a good idea compared to having to do SPA's without it. Try doing a SPA with only jQuery.

VDOM is also a good idea that simplifies the mental model tremendously. Of course these days we can do better than a VDOM. Svelte in fact doesn't use a VDOM. You can say that VDOM is a terrible idea in comparison with Svelte, but that's just anachronistic.

Re: The GitHub website is slow on Safari

#214

Post by humpty-d »

lowwave wrote: post #203
mrbombastic wrote: post #143

Earlier quoted context omitted.

M4 macbook pro and almost unusably slow

Ah the wonders of SPA! I know there are lighter ones, but it is not the first time hearing things like React being slow. Of course, when one start to do sntax highlighting on the client side....

Various comments and links throughout the discussion of this post indicate that the problem is a mix of the sheer number of nodes and css. It has nothing to do with React or being a React SPA, which it's also not, unless you have some proof otherwise.

Re: The GitHub website is slow on Safari

#215

Post by Tadpole9181 »

lowwave wrote: post #203
mrbombastic wrote: post #143

Earlier quoted context omitted.

M4 macbook pro and almost unusably slow

Ah the wonders of SPA! I know there are lighter ones, but it is not the first time hearing things like React being slow. Of course, when one start to do sntax highlighting on the client side....

> When native software is slow, it's bad software. When web software is slow, react is bad software.

This is such a tired trope.

Re: The GitHub website is slow on Safari

#216

Post by whstl »

veverkap wrote: post #191
whstl wrote: post #33

Earlier quoted context omitted.

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? :)

What's that, a Github employee? Not really, I'm in an YC startup.

But I guess the problem is that every single development position has been converging into this.

The only times in my career as a developer where I was 100% happy was when there was no career PM. Sales, customers, end-users, an engineering manager, another manager, a business owner, a random employee, some rando right out the street... All of those were way better product owners than career PMs in my 25 years of experience.

This is not exactly about competence of the category, it's just about what fits and doesn't. Software development ONLY work when there is a balance of power. PMs have leverage that developers rarely have.

I come from Electrical Engineering. Engineering requires responsibility, but responsibility requires the ability to say "no". PMs, when part of a multi-disciplinary team, make this borderline impossible, and make "being an engineer" synonymous with putting a target on your back.

Re: The GitHub website is slow on Safari

#217

Post by ants_everywhere »

tk401 wrote: post #167
ants_everywhere wrote: post #81

Earlier quoted context omitted.

[flagged]

That the optimization pressure imposed by "capitalist masters" can lead to perverse outcomes does not imply that the optimization pressure imposed by communist ones doesn't, surely? For instance, the GP could be a proponent of self-management, and the statement would be coherent (an indictment of leaders within capitalism) without supposing anything about communism.

Yet another new account that has only a single comment replying to me. I've noticed this is a pattern.

At any rate your point doesn't make any sense. The same point indicts all leaders, it has nothing to do with capitalism. It's like saying something indicts a specific race of people when it applies to all people equally.

Re: The GitHub website is slow on Safari

#218

Post by makeitdouble »

Autummata wrote: post #185
makeitdouble wrote: post #155

Earlier quoted context omitted.

> hilariously probably Windows That's probably true. > 15 y/0 It's a matter of expectations, many laptops that old still work decently enough with a refreshed battery. Funnily enough win10 was released 15 ago, and one can still get support for it for at least another 3 years until 2028, even on the customer license.

W10 was released 10 years ago, not 15. https://en.wikipedia.org/wiki/Windows_10_version_history

Sorry, I just have pattern matched the 2015 release year instead of properly counting.

Re: The GitHub website is slow on Safari

#219

Post by estimator7292 »

PedroBatista wrote: post #11

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…

[dead]

Re: The GitHub website is slow on Safari

#220

Post by estimator7292 »

ballenf wrote: 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 end-user experience is not of any concern in modern tech. None at all. The only thing that matters is engagement hacking and middle managers desperately trying to look like they're doing anything with any value or meaning at all.
Post reply on HN