3 ms·

I think GP is saying, if you are at a point in development where you can choose A or B, and A has foreseeable better performance or scalability, all else being

I think GP is saying, if you are at a point in development where you can choose A or B, and A has foreseeable better performance or scalability, all else being equal choose A. A lot of assumptions there and real world is almost never that clear-cut. The general advice of "don't optimize until you've measured" is still almost always correct.

magicalhippo 8y ago
> The general advice of "don't optimize until you've measured" is still almost always correct. The issue of course being that when designing code, various design choices can have significant performance implications, and can be very hard to change once implemented and in production.