3 ms·
Sounds like you’re saying that you’ve been able to make any language fast enough where performance is not critical, but that you realize that when it is (you me
by leephillips 5y ago
Sounds like you’re saying that you’ve been able to make any language fast enough where performance is not critical, but that you realize that when it is (you mention HFT, but there is also HPC for science and engineering, a vast area), the slow languages won’t cut it. I can’t disagree, but your comment also seems like a bit of a tautology.
- naniwaduni 5y agoI think GP is implying a stronger point than you're making it out to, that the situations where performance is critical occur "only in extremely specific scenarios", backed by the claim that they've managed to avoid such scenarios for 7~15 years.
- shados 5y agoThat's kind of like saying that a backend developer has managed to avoid needing a frontend component frameworks for 20 years, so the need for such a framework is rare. It's a self fulfilling prophecy. The OP didn't pick jobs completely randomly, I assume, so they're mostly going to be working around their specific skillset, which may just not require performance critical work. If they worked at Nvidia, Intel, or Epic Games on low level engines, they could flip that around and say they haven't been in a situation where perf wasn't one of their top priorities.