Live data from Hacker News

The GitHub website is slow on Safari

github.com

271–280 of 367 posts

Re: The GitHub website is slow on Safari

#271
post #202

This thread has really opened my eyes to how much the world hates react developers, I am one. Unrealistic timelines, implementing what should be backend logic in frontend, there's a bunch of ways SPA's tend to be a trap. Was react a bad idea? Can anyone point to a single well made react app?

After having worked on React for a while, I can tell you that the problem remains between monitor and chair. React can have all the niceties and optimization in the world, but that fails when its users insist on using it incorrectly, building huge tangled messy components and then wondering why a click takes 1.3 seconds to deliver feedback.

The problem that is that react doesn't have a pit of success. Because it's poorly conceived, poorly designed and poorly written software made by people more interested in getting the word "homomorphism" onto their CV than solving real problems. You knew when they started using terms like "monad" and "functor" in order to attach a click handler to a button that something had gone badly wrong.

In this very thread there's some asshole using the word "memoization" when "caching" would have been fine.

Re: The GitHub website is slow on Safari

#272
post #5

Improvements merged within the last two days by the WebKit team: https://github.com/orgs/community/discussions/170922#discuss... For my sins I occasionally create large PRs (> 1,000 files) in GitHub, and teammates (who mostly all use Chrome) will sometimes say "I'll approve once it loads for me..."

Interesting how _everyone_ here blames JS and React, yet the fixes you linked are about CSS performance.

These performance problems are new since a rewrite which also added react. Could be just a coincidence, but that is why people blame react.

Re: The GitHub website is slow on Safari

#273
post #268

Earlier quoted context omitted.

React and the most commonly used pattern inherently promotes an way to complex html Node structure and shitty css, especially if stuff like tailwind is used. Now you CAN so it so that is not the case, but tbh i have never seen that in the wild -

Lol. If anything, Tailwind isn't shitty CSS (because it's a very limited number of classes) unlike the gazillion one-off classes that CSS-in-JS or even BEM encourages Edit: here's a good investigation on a real-enough app https://www.developerway.com/posts/tailwind-vs-linaria-perfo...

Yes what's with his comment?

Tailwind is probably one of the best considering you can use Vite to literally strip out all unused css easily.

And I think tailwind v4 does this automatically

Re: The GitHub website is slow on Safari

#274

Earlier quoted context omitted.

> When native software is slow, it's bad software. When web software is slow, react is bad software. This is such a tired trope.

Its not really a trope, the opposite is much more common. People are much more quick to mindlessly blame SSR for slowness like with ROR or PHP. The reality is both can be slow, it depends on your data access patterns, network usage, and architecture. But the other reality is that SPAs and REST APIs just usually have less optimal network usage and much worse data access patterns than traditional DB connected SSR monol…

React also has a class of problems that doesn't really happen in other types of apps: re-renders.

Even other frameworks like Vue.js, Solid or Svelte don't really suffer from it as much. It simply happens a couple order of magnitudes more often in React than any other framework.

Re: The GitHub website is slow on Safari

#275

Earlier quoted context omitted.

Lol I respect that https://muan.co/no-yc/

Based tbh

I love the explanation in the linked site:

> Writing on the internet can be a two-way thing, a learning experience guided by iteration and feedback. I’ve learned some bad habits from Hacker News. I added Caveats sections to articles to make sure that nobody would take my points too broadly. I edited away asides and comments that were fun but would make articles less focused. I came to expect pedantic, judgmental feedback on everything I wrote, regardless of what it was.

https://macwright.com/2022/09/15/hacker-news

Which is true. Pedantism is the lowest form of pseudo-intelligence.

Re: The GitHub website is slow on Safari

#276
post #225

Earlier quoted context omitted.

Have you used gitlab every day in anger? I don't think you'd feel the same if you have.

There's things I don't like about it, and there are a looot of long-standing open issues, but I think GitLab is definitely better than GitHub in a number of ways. My org uses both (and also Azure DevOps, joy) and my team expects that the trend will be migrating from GitLab to GitHub. There are a bunch of things for me to grieve in that, much to my own surprise.

We use a self-hosted GitLab for about 6 years now. The only thing that is really awful is if your MR gets too big. Then GitLab will simply stop showing any code changes above a certain line threshold.

Re: The GitHub website is slow on Safari

#278
post #204

Earlier quoted context omitted.

And to be fair, the problems that Facebook had when they introduced React are not common problems at all. As an aside, I was an employee around then and I vividly remember that the next half there was a topline goal to improve web speed. Hmmmm, I wonder what could have happened?

> And to be fair, the problems that Facebook had when they introduced React are not common problems at all. That’s one of my favorites. The exact bug they described during React launch presentation, that React was supposed to help fix with the unidirectional dataflow. You know the one where unread message badges were showing up inconsistently in the UI in different places. They never managed to fix that bug in the 10…

To be fair, that bug increases engagement so it'll never be fixed. All must kneel before Deltoid/QRT!

Re: The GitHub website is slow on Safari

#279
post #83

Isn't the opposite? No one in this thread even cogitating how bad Safari is in terms of performance and supporting web standards? There's in one even partially blaming both. Github isn't the best example of a fast website, but if you can run it in Chrome and Firefox, even on rudimentary browsers like Palemoon (I tested) on decent hardware (even mobile), there's something clearly wrong on Safari.

Because a lot of apple fanboys everywhere, they'd rather blame the whole web than the shitty apple software.

Re: The GitHub website is slow on Safari

#280
post #132

This thread has really opened my eyes to how much the world hates react developers, I am one. Unrealistic timelines, implementing what should be backend logic in frontend, there's a bunch of ways SPA's tend to be a trap. Was react a bad idea? Can anyone point to a single well made react app?

> a single well made react app What about Slack, the messenger? Umm, Discord? SoundCloud? Trello? Bandcamp? Spotify? If I keep going there are actually hundreds and thousands of well-made react apps.

Slack on my machine is currently taking ~1GiB of memory and 3% cpu to do nothing.

My irc client is taking 60MiB of memory and 0.01% cpu. My IRC client is responsive and faster, it has more configurable notification settings. I like the irc client more.

> Bandcamp

I just went to the bandcamp page and it indeed loaded very quickly. As far as I can tell, there's no react in use anywhere so I guess that's why.

What do you mean by bandcamp using react?

Post reply on HN