> the web would be a much better place if opening the Chrome developer tools automatically enabled the network throttler, and I think I’d have to agree with him

> the web would be a much better place if opening the Chrome developer tools automatically enabled the network throttler, and I think I’d have to agree with him. This. And if it could also throttle CPU performance, painting performance, and available cache memory to a "typical user" profile that would be ideal. It would be best of all if that typical profile varied from day to day to cover a range of experiences of typical users, but the distribution was updated periodically from the lower quartile of the general web user population as measured by surveys. In general: Fast developer machine for builds, slow runtime machine for using the application. (In embedded and console games this has always been automatic :-) If you don't run the application on a separate machine, then simulate one instead. But there's no advantage in making IDEs, compiles and testsuites run slowly. Just the target application.