81–90 of 321 posts
I just put the throttling on in the network tab of Firefox/chrome developer tools. Plenty realistic
There is something very pleasing about everything running smoothly without any hiccups.
Or, do not endorse people's bad buying patterns. I do care about crappy network and load times. But there's some laptop that have worse performances than three years old tablets, and there seems to be no end to what scummy companies sell at low end. At some point down the crappy pit, there's a line where it's no longer my problem.
I mean, I know a guy who recently got into frontend development with react. I did the backend for an app he was building. I had to explain him what an XMLHttpRequest is so he could send me one. It just blows my mind that there are people who legit write code with some framework but don't know the basics of the language they're writing in and/or the platform the whole thing runs on.
Gmail has nearly 50mb of JavaScript that thrashes I/O so hard that clicking the search bar and typing too soon will cause it to skip letters (because the search bar is probably some Angular-powered abomination). It is and was a regression from the previous design which was fast even on 3G connections. It's driven by Google engineers running their bloatware on i9 MBPs with 64gb of RAM. Oh Gmail is slow? Have you tried…
They do still support the basic HTML version: https://mail.google.com/mail/u/0/h/
There are three kinds of web developers: - Those who don't care about performance, as long as it loads within a few seconds on their own beefed up system on the LAN. This article is for them, and we can only hope they will listen. - Those who care about performance, and work for people who care. They are already doing great work (or are about to), producing those rare low-friction, high-speed, content-is-king sites w…
unless faang companies suddenly make it trendy again to care about low fidelity experience.
> Because of the rise in injuries, British command considered going back to the drawing board with the helmet’s design. Fortunately, a statistician pointed out that the dramatic rise in hospital cases was because people were surviving injuries that previously would have killed them—before the introduction of steel the British Army used felt or leather as headwear material.
I've seen this same story except with warplanes during the War. Story goes that an allied air force tried to improve the percentage of planes that would return from a bombing raid, so they inspected returning planes, found the places where they had holes in them and added extra layers of steel to those areas for the next bomb run; but this had no improvement on the percentage of planes that returned.
That is until a "statistician" realized that all of the places on the plane that they found holes in were actually parts of the plane that could get hit and survive and return. They then started adding extra steel to the parts of the planes they found no holes or damage assuming that if those parts were hit the plane would get shot down and not return. After this change they started seeing a dramatic increase in the amount of planes returning from a raid.
Does anyone know the true source of these stories?
Regardless, it really opened my eyes to how changing your perspective on the cause of the problem can help find the best solution, and to this day I still think of this story when solving a problem.
There are three kinds of web developers: - Those who don't care about performance, as long as it loads within a few seconds on their own beefed up system on the LAN. This article is for them, and we can only hope they will listen. - Those who care about performance, and work for people who care. They are already doing great work (or are about to), producing those rare low-friction, high-speed, content-is-king sites w…
Explain Gmail.
Earlier quoted context omitted.
Unless you mean that the menu is hidden behind the gear icon, calling it a hidden feature is a stretch. https://developer.chrome.com/docs/devtools/device-mode/#cpu
Sufficiently deep in menus that I suspect most people here on HN would consider themselves familiar with devtools, yet wouldn't have been aware of this option.
To be honest, this feels like the author never used "craptop". WSL even with quad-core hasewell laptop and 8GB is pushing it. It's better to RDP / develop on one machine and run on another.
Having said that, It's important to test on low speced always. Even not for website (we test our cpp code on some 2009 machines)
> British soldiers in World War I were equipped with a Brodie helmet, a steel hat designed to protect its wearer from overhead blasts and shrapnel while conducting trench warfare. After its deployment, field hospitals saw an uptick in soldiers with severe head injuries. > Because of the rise in injuries, British command considered going back to the drawing board with the helmet’s design. Fortunately, a statistician p…
Even more than crappy laptop, please please test your application on bad/degraded networks. So many apps completely glitch and breakdown in bad network environments.
It's frustrating that this is so easy to do in one click using the browser's in-built developer tools, and yet no dev team spends their time on it (or even know that it exists).
On windows I used clumsy that was much more realistic. On some tablets, I used my microwave oven or my feets to walk away from the Wi-Fi.