4 ms·
Hardware is so cheap that we have the luxury of optimizing for developer time, which keeps getting more expensive. Cranking out over a hundred lines to do “almo
by erik_seaberg 3y ago
Hardware is so cheap that we have the luxury of optimizing for developer time, which keeps getting more expensive. Cranking out over a hundred lines to do “almost nothing” is not a good use of time, and 200 kqps without concurrency isn’t realistic unless you blow all your memory on caching everything (your single-core time budget is 5 µs!)
- mkristiansen 3y agoI'm not sure the line count is a good measure of productivity. Is that true on the note of "optimizing for developer time"? Do people actually have an understanding of the tradeoff they are making? Do the teams building applications in Java actually know what it would take to do them in C, and choose that the tradeoff is too big? Does the Typescript backend developer know what it would take to do the same in C++ and decide against it? Or are they mainly working out of a preconceived bias that their favorite language is best and that everything else is worse? For the 5 µs, I recall a currency conversion system(tin-cup) with in-memory currency rates whose only job was to convert incoming requests to USD. Ignoring the fact that this should never have been an independent system. This seems like a perfect use case for working in a highly optimized environment. ;)