3 ms·

Another trick to deal with heavy web requests is artificially limiting bandwidth. By simulating a slow 3G connection using devtools (yes, its a feature!), devel

Another trick to deal with heavy web requests is artificially limiting bandwidth. By simulating a slow 3G connection using devtools (yes, its a feature!), developers should see how much time does it take to load. Personally, I would love to see the slow 3G speed the default

onion2k 5y ago
I think it would be great if devtools had a very prominent and easy to enable "test mode" that switched on a few settings like network and CPU throttling. It should be a top level tab like Elements and Recorder.
- bityard 5y ago
  If browsers were to artificially limit network speeds, it would force web page authors to slim down their pages, which would in turn reduce the aggregate costs to run servers, backbone links, and last-mile connections in developing countries and the rural US. Maybe as a nice bonus, we'd get fewer auto-play videos on websites that the browser authors somehow still haven't figured out how to prevent. Anyway, it would be far from the first time the web browsers have thrown their weight around to effect changes across the whole Internet...
  - onion2k 5y ago
    If browsers were to artificially limit network speeds, it would force web page authors to slim down their pages... I wish that was true. The truth is that a lot of developers don't know how to do that work, or that don't care, or (very weirdly in my opinion) are actually proud of the fact they build a huge and bloated app. Moreover though, sometimes those large apps are actually relevant. Having a background video on a brochure site isn't automatically a bad thing - those features can and do drive sales. You might disagree with that about some feature you don't like, but chances are there's some other feature you do like that other people would happily limit because they don't need it. We should be wary of imposing limits on everything because we would lose some things that are actually good for some users. To use a lovely British idiom, let's not throw the baby out with the bath water.

onion2k 5y ago

I think it would be great if devtools had a very prominent and easy to enable "test mode" that switched on a few settings like network and CPU throttling. It should be a top level tab like Elements and Recorder.

bityard 5y ago
If browsers were to artificially limit network speeds, it would force web page authors to slim down their pages, which would in turn reduce the aggregate costs to run servers, backbone links, and last-mile connections in developing countries and the rural US. Maybe as a nice bonus, we'd get fewer auto-play videos on websites that the browser authors somehow still haven't figured out how to prevent. Anyway, it would be far from the first time the web browsers have thrown their weight around to effect changes across the whole Internet...
- onion2k 5y ago
  If browsers were to artificially limit network speeds, it would force web page authors to slim down their pages... I wish that was true. The truth is that a lot of developers don't know how to do that work, or that don't care, or (very weirdly in my opinion) are actually proud of the fact they build a huge and bloated app. Moreover though, sometimes those large apps are actually relevant. Having a background video on a brochure site isn't automatically a bad thing - those features can and do drive sales. You might disagree with that about some feature you don't like, but chances are there's some other feature you do like that other people would happily limit because they don't need it. We should be wary of imposing limits on everything because we would lose some things that are actually good for some users. To use a lovely British idiom, let's not throw the baby out with the bath water.