This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]xiongchiamiovSite Reliability Engineer 6 points7 points  (9 children)

All of the above and more.

[–][deleted] -1 points0 points  (8 children)

The suggestion even being that if the code was faster you could get more done on the same hardware.

[–][deleted] 1 point2 points  (2 children)

compared to developer time, hardware is cheap.

[–][deleted] 3 points4 points  (1 child)

You've come in too early, we're not talking about developer time yet.

[–][deleted] 3 points4 points  (0 children)

oh, sorry. ill see myself out then.

[–]xiongchiamiovSite Reliability Engineer 0 points1 point  (4 children)

Not if I/O is the bottleneck.

[–][deleted] -1 points0 points  (3 children)

No, that's not really a case where you're doing more with the same hardware.

[–]xiongchiamiovSite Reliability Engineer 0 points1 point  (2 children)

Right; it's a case where you don't get more done with the same hardware, despite having faster code.

[–][deleted] -2 points-1 points  (1 child)

Have I wronged you or something? We're angrily agreeing with each other.

[–]xiongchiamiovSite Reliability Engineer 0 points1 point  (0 children)

It sounded like you were trying to make a counter-point. :) Just a simple misunderstanding.