2 ms·
You can be immature going the other direction, too. "We need to squeeze every last cycle of performance out of this server before we buy another one." Well, so
by kabdib 10y ago
You can be immature going the other direction, too. "We need to squeeze every last cycle of performance out of this server before we buy another one."
Well, sometimes you do (when it's someone else's hardware, perhaps). But often, happiness is a middle ground.
Most hardware goes through phases, often planned far in advance: The expensive first version to get something out the door, then a series of cost reductions (bring many chips into a single custom chip, ditch unused features, get new vendors for subsystems) which improve profitability.
That juicer looks like it was designed to withstand a direct hit by a bunker buster. Nobody gave a damn about profit margins or ever making it cheaper, I think they just wanted to IPO or get bought.
- sidlls 10y agoWell sure immaturity exists in every axis. I've seen "performance zealots" seriously suggesting moving a perfectly functional internal flask based API into some obnoxious, bloated Java Spring something or other to squeeze performance out of it. The thing served approximately 1 (internal) user at a time at a rate of less than 1 request per minute on average and was a read-only API. Flask was just fine for the purpose. I've also been guilty of this in my younger days, where I was very much "C++ all the things because performance." But that's kind of my point: it's immaturity at work, here.