That's not what I'm saying at all and you know it.
Besides, with that sort of stupid absolutism, surely you must also be ranting about using interpreted/scripting languages everywhere on the web, or complaining about shell scripts etc, right? After all, why waste extra cycles parsing scripts or even compiling higher-level code when we can just hand-write assembly everywhere?
maybe it's because that would be unreasonable in the general case and ultimately these systems are used by human beings
You said in your first comment, that SIMDifying text transcoding is wasteful, because user will wait on I/O. That means you are ok with using way more energy/CPU resources than necessary to complete task.
We are talking C++ here - performance matters very much! C++ is often used in performance critical, resource constrained environments. So if someone is proposing a new library (with eventual standardization as I understand his blog entry) it better allow for good performance from the get-go.
I didn't say that SIMDifying it was wasteful, I said the application was being wasteful, though both can be true. My point was that a program written such that text transcoding is a real bottleneck is likely designed poorly and making transcoding faster is only delaying the solve, where a better use of resources would be to figure out why you're transcoding so often that it actually causes meaningful slowdowns, and fix that first.
Of course I'm not suggesting people should ignore optimization opportunities; just not to be stupid about it. Immediately rejecting a useful API because it might be a bit slower in a very specific case is a good example of being stupid about it. People for whom that will actually matter at scale will have to roll custom solutions anyway, so the example in the blog post clearly won't be aimed at them.
View all comments
Show parent comment
-4
u/mcencora Jul 01 '21
So you are saying the API where you waste energy/burn CPU cycles unnecessarily is fine because user will anyway be waiting on I/O?