Indeed, I should drop the agression.
However, the subject is not optimization but coding correctly in the first place.
And the anti-optimization argument would be correct if:
-typing represented more than 1% of dev work
-code was never reused
-code was never massively used
-code had a short lifespan
So let me help you see clearly:
-I'm not a typist
-Every bad code tutorial out there creates millions of code bits that contain the N times slower version, with an aggregate impact that actually matters
-Any 10% opt mistake in a codebase like iptables would cause more carbon than you can imagine
-Fortran is still in use because it's the fastest language there is with the best math libraries.
Those seem to be eternal so far, and C seems to remain the only other relevant language throughout the short history of coding.
Sure, there are much more problematic cases than the dumb even odd example, but I picked that one because many would recognize it.
And the anti-optimization argument would be correct if: -typing represented more than 1% of dev work -code was never reused -code was never massively used -code had a short lifespan
So let me help you see clearly: -I'm not a typist -Every bad code tutorial out there creates millions of code bits that contain the N times slower version, with an aggregate impact that actually matters -Any 10% opt mistake in a codebase like iptables would cause more carbon than you can imagine -Fortran is still in use because it's the fastest language there is with the best math libraries.
Those seem to be eternal so far, and C seems to remain the only other relevant language throughout the short history of coding.
Sure, there are much more problematic cases than the dumb even odd example, but I picked that one because many would recognize it.