5 ms·
I agree with you. There are way too many cases of people making generalized arguments "you shouldn't do XYZ in programming because it's slow/confusing/etc" that
by moron4hire 14y ago
I agree with you. There are way too many cases of people making generalized arguments "you shouldn't do XYZ in programming because it's slow/confusing/etc" that really just have no place being uttered unless they can show mathematical proof it is too much to bother with in every situation. Back in the 80s and early 90s it was "no compiled language should ever be used for critical software", and then in the late 90s and early aughts it was "no VM'd language". Now what? It's all there is! You'd be nuts to NOT use a VM'd language. And the only reason we know any better is because people ignored the received wisdom and just did their own thing.
Keep doing your own thing.
- andyjpb 14y agoI generally agree but I'd replace "unless they can show mathematical proof" with "unless they can show a code profile". Happy days!
- moron4hire 14y agoI get your point, and that's pretty much what I meant. You need to have very specific reasons. I would argue a code profile would only prove a specific case, instead of a general case. But the point remains, "best practices" aren't theorems. They are used by more programmers as CYA than as good software development strategies.
- yread 14y agoMaybe I'm getting old but VM'd language shouldn't be used for critical software. Critical as in real-time or literally life-or-death situations. Also how should a a mathematical proof that code that uses exceptions for jumping out of iteration doesn't confuse anybody look like? It's just confusing because it's never done like that. It confuses programmers. At least one. QED? You CAN devise your own coding style, but when using the conventions reader can safely assume couple of things. Reading code that doesn't follow these conventions is more difficult (for everybody except you).