It has to present text lists, tables and small icons. Makes mobile Safari crawl to a halt. With multi gigahertz, multi core cpus and hardware accelerated js. It is pathetic.
The GitHub website is slow on Safari
241–250 of 367 posts
Re: The GitHub website is slow on Safari
#242Can 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?
In the old days we had the saying: "Nobody ever got fired for buying IBM" Todays version is: "You will get fired unless you use React". So every site now uses React no matter if the end result is a dog slow Github. Bad developers looks at "what are everybody else using?". Good developers looks at "what is the best and simplest (KISS) tool for this?"
> Good developers looks at "what is the best and simplest (KISS) tool for this?"
Good ol’ SSR - but eventually users and PMs start requesting features that can only be implemented with an SPA system, and I (begrudgingly) accept their arguments.
In my role (of many) as technical architect for my org, and as an act of resistance (and possibly to intentionally sabotage LLMs taking over), I opted for hybrid SSR + Svelte - it’s working well for us.
Re: The GitHub website is slow on Safari
#243This 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?
Been a huge React/SPA fan for many years, until the realization began to creep on me that building them was actually harder than building C++ MFC desktop applications (which I did back in the 2000's). Declarative markup was supposed to reduce cognitive load, but it now feels like the interplay between the declarative part of UI development (component markup) and the procedural part (event handling and state) has slow…
Last couple years I built a largish javafx app and this was the entire way I structured it. A little tedious, but if I have a state management issue it's just logic on my side and not ten layers of abstraction.
Re: The GitHub website is slow on Safari
#244Earlier quoted context omitted.
Servers cost money, the client is free (and pays you sometimes)!
The client costs money too, opportunity cost. Which, unfortunately, cannot be measured :( so no KPIs. Darn! Its all fun and games until you cut quality over and over so much your customers just leave. Ask Chrysler or GE. I mean they must have saved, what, billions across decades? And for free! Well... um... not free actually, because those companies have been run into the ground, dragged through hell, revived, and th…
MBA's ruin everything
Re: The GitHub website is slow on Safari
#245This 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?
Been a huge React/SPA fan for many years, until the realization began to creep on me that building them was actually harder than building C++ MFC desktop applications (which I did back in the 2000's). Declarative markup was supposed to reduce cognitive load, but it now feels like the interplay between the declarative part of UI development (component markup) and the procedural part (event handling and state) has slow…
what does MFC mean?
Re: The GitHub website is slow on Safari
#246Earlier quoted context omitted.
Been a huge React/SPA fan for many years, until the realization began to creep on me that building them was actually harder than building C++ MFC desktop applications (which I did back in the 2000's). Declarative markup was supposed to reduce cognitive load, but it now feels like the interplay between the declarative part of UI development (component markup) and the procedural part (event handling and state) has slow…
Last couple years I built a largish javafx app and this was the entire way I structured it. A little tedious, but if I have a state management issue it's just logic on my side and not ten layers of abstraction.
That's a good way to put it. A bit tedious, but the mental model is relatively simple. Reading and writing code feels a little closer to riding a bicycle than operating a Rube-Goldberg device.
Re: The GitHub website is slow on Safari
#247Earlier quoted context omitted.
Been a huge React/SPA fan for many years, until the realization began to creep on me that building them was actually harder than building C++ MFC desktop applications (which I did back in the 2000's). Declarative markup was supposed to reduce cognitive load, but it now feels like the interplay between the declarative part of UI development (component markup) and the procedural part (event handling and state) has slow…
what does MFC mean?
The Microsoft Foundation Class library: https://learn.microsoft.com/en-us/cpp/mfc/reference/creating...
Re: The GitHub website is slow on Safari
#248huh? I never felt it to be slow on Safari, using em for years now.
Re: The GitHub website is slow on Safari
#249The 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…
I went several years without having to interact with Github, I came back to it this year and it was truly shocking how bad it's gotten.
I had to alter basically every aspect of how I interact with it because of how fucking slow it is! I still can't shake the sense that it's about to go down or that I've done something wrong every time I click something and nothing happens for several seconds.
Re: The GitHub website is slow on Safari
#250Earlier quoted context omitted.
i mean there are also lots of browser options to be fair. should they be locking safari to the OS, definitely not. but users can just go download another browser if they are actually concerned.
Will modern versions of those other browsers still work on an 8 year old OS, or has it been updated where it is no longer compatible? So much effort has been put into hardware rendering, and the mechanisms for the browser to interact with that hardware has changed within those OS versions. Forcing the user to download an older compatible version of the browser to work with the older OS is also tossing away potential…
i mean you're also throwing away security fixed running an OS that out of date, but the person doing this probably doesn't care about security anyway.