Earlier quoted context omitted.
Never heard anyone complaining either./
Try meeting people who use slack?
The GitHub website is slow on Safari
351–360 of 367 posts
Re: The GitHub website is slow on Safari
#352Re: The GitHub website is slow on Safari
#353Earlier quoted context omitted.
As someone who's worked with React professionally for years, it's honestly shocking how few React developers really understand memoization and when it needs to be used IMO it's the MAIN thing to understand about React—how it renders. Regardless, now I'm the one with egg on my face since the new compiler promises to eventually remove the need for manual memoization almost entirely. The "almost" still fills me with fea…
Is there a good article or something you could point us younglings to? I get that in react almost everything is reactive by default unlike other frameworks. I tend to add useCallback and memo to everything nowadays.
https://alexsidorenko.com/blog/react-render-always-rerenders
It's a set of 6 short and sweet posts that breaks down rendering behavior, memoization, and relevant hooks
Re: The GitHub website is slow on Safari
#354Earlier quoted context omitted.
the problem is developers having fast modern machines. if they were forced to use slow machines, they would not be able to put out crap like that
While I agree about devs should be testing on slow devices, the particular target audience of the site generally have pretty decent machines (including two that I have) and there isn't much reason for the site lag. It's not really doing any 3D rendering with complex shaders or video filtering; it just shows changed lines in two files. That shouldn't lag.
Re: The GitHub website is slow on Safari
#355Earlier quoted context omitted.
> Is it your theory that working on large projects was better when you had communist masters? It is. Unemployment was virtually non-existant in the ussr, and healthcare was not connected to employment status. So a worker there knew that saying no to their boss was not going to be a life-or-death decision. They might of course be less wealthy and so on but the worst case didn't look as bad.
This is false, striking was illegal in the USSR. If you refused to do work you were an enemy of the state. If your town didn't meet the farming quota they would starve your entire town. If you went on strike you would get murdered and sometimes your family would get murdered. If you deserted from the army or retreated you would get shot by barrier troops. If you were injured or sick you would be disposed of or hidden…
Re: The GitHub website is slow on Safari
#356Re: The GitHub website is slow on Safari
#357The 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…
Re: The GitHub website is slow on Safari
#358Re: The GitHub website is slow on Safari
#359GitHub moved to a JavaScript rendering mode almost as soon as Microsoft bought it. Previously, I had been able to browse it with JavaScript disabled on my 2011 Mac Mini which Apple stopped allowing upgrades on past macOS 10.13. So even if I enable JavaScript, I can no longer browse GitHub, because they didn't bother to make their build compatible with browser versions as old as mine. It's hard to know which member of…
Re: The GitHub website is slow on Safari
#360A regular GitHub annoyance for me is the propensity to lose the browser history for the main repo page. On random site, Navigate to GitHub repo, navigate to file in repo, and hit back, and I'm on the random site, hit forward and I'm on the file. So annoying. One of a large handful of issues I've encountered post react conversion
Any time I click a GitHub link, if I navigate beyond the readme, then my history is completely borked. Going “back” one page might go to the readme, might go back to HN, or might even go back to the readme and then back to the page I was trying to leave!
It’s infuriating and I always figured it was a bug they’d fix eventually but it’s been at least two years of this crap.