3 ms·

I think that would be true for testing, but not for actual development. When I'm working I want to marginalize anything that might slow me down. You did mention

I think that would be true for testing, but not for actual development. When I'm working I want to marginalize anything that might slow me down. You did mention the build machine should be fast - but don't most people build locally first before pushing out? I guess it also depends on what you're building. I mostly work on stuff that isn't used by a consumer. It's going to run as a service on a machine or network of machines far more powerful than my PC. I imagine most people developing for consumers though are building websites or mobile apps. Mobile apps should be tested on a variety of devices, and it would take a pretty intense website to start bogging down most people's machines I imagine.

pyre 16y ago
> it would take a pretty intense website to start bogging down > most people's machines I imagine. Not necessarily. On an internal website we found that IE8 took 8 seconds (!) to run a jQuery/jQueryUI command to style all of the buttons on a page. Granted there where more than a couple of buttons, but the point is that DOM manipulation can be a time sink if you don't manage it right. (By contrast the same command took ~1s in Chrome and Firefox, which still isn't insignificant).
- ryanpetrich 16y ago
  One second of DOM manipulation _is_ significant.
  - pyre 16y ago
    > which still isn't insignificant An extra second of page load isn't as noticable as 8 extra seconds of page load. Especially on older systems where you might be used to some amount of delay (but not 8 seconds of delay on internal apps).
    - ryanpetrich 16y ago
      I guess it depends on what your baseline is. For most of my pageviews, an additional second would double the load time. On an internal app/site an additional few seconds usually isn't worth the trouble, but externally can make a real difference: http://www.zdnet.com/blog/btl/googles-marissa-mayer-speed-wins/3925 http://www.zdnet.com/blog/btl/googles-marissa-mayer-speed-wi...
jmtulloss 16y ago
I have no trouble writing JavaScript that brings the mightiest of machines to its knees. I try not to ship that, of course.

pyre 16y ago

> it would take a pretty intense website to start bogging down > most people's machines I imagine. Not necessarily. On an internal website we found that IE8 took 8 seconds (!) to run a jQuery/jQueryUI command to style all of the buttons on a page. Granted there where more than a couple of buttons, but the point is that DOM manipulation can be a time sink if you don't manage it right. (By contrast the same command took ~1s in Chrome and Firefox, which still isn't insignificant).

ryanpetrich 16y ago
One second of DOM manipulation _is_ significant.
- pyre 16y ago
  > which still isn't insignificant An extra second of page load isn't as noticable as 8 extra seconds of page load. Especially on older systems where you might be used to some amount of delay (but not 8 seconds of delay on internal apps).
  - ryanpetrich 16y ago
    I guess it depends on what your baseline is. For most of my pageviews, an additional second would double the load time. On an internal app/site an additional few seconds usually isn't worth the trouble, but externally can make a real difference: http://www.zdnet.com/blog/btl/googles-marissa-mayer-speed-wins/3925 http://www.zdnet.com/blog/btl/googles-marissa-mayer-speed-wi...

jmtulloss 16y ago

I have no trouble writing JavaScript that brings the mightiest of machines to its knees. I try not to ship that, of course.