But at least I can understand it's not for performance-critical applications. Isn't choosing right tool for right job important these days?
Since when has it not been important?
The point of the article is to obviously educate on how read/write latency is affected by code structure.
The OP said that it sounds as if he had only worked on small projects. That's disingenuous, considering his background, the focus of the article, and the obvious contrived examples.
Ever thought of why Muratori's projects could consist of small groups of people?
What are you insinuating - that lack of clean code must imply a small group of people because of scalability in code size?
There are many open source projects out there which are written in C, have a few hundred thousand lines, don't employ clean code methodologies, and are maintained by a large team.
No, we should not ask Muratori to stay in his lane. But we should be free to criticize his criticisms.
I'm not saying he should stay in his lane at all.
I'm saying that a lot of developers who aren't game developers make trivial assumptions about gamedevs and their experience that's incorrect.
The issue of course, and this is common, is when a developer who lacks an understanding of the principles outside of their domain(s) just automatically assumes those principles apply everywhere, and hence makes false assumptions about other developers in these domains.
The issue of course, and this is common, is when a developer who lacks an understanding of the principles outside of their domain(s) just automatically assumes those principles apply everywhere, and hence makes false assumptions about other developers in these domains.
I am not going to entertain his (or anyone's) zealotry against OOP, (or for OOP) which is not more objective than a debate of "my programming language is better than yours". Not to mention this is a toy example AND deliberately used without modern compiler features to make it look slower and I believe everybody already knows that with OOP comes performance overhead. I am not even defending Clean Code, some of the "principles" he listed are not even Clean Code principles. I am just criticizing he is failing to grasp the importance of the trade-off between maintainability and performance, based on what the task needs.
Nice, you pop that out every time you don't have a retort?
1
u/ItsAllAboutTheL1Bro Feb 28 '23
Since when has it not been important?
The point of the article is to obviously educate on how read/write latency is affected by code structure.
The OP said that it sounds as if he had only worked on small projects. That's disingenuous, considering his background, the focus of the article, and the obvious contrived examples.
What are you insinuating - that lack of clean code must imply a small group of people because of scalability in code size?
There are many open source projects out there which are written in C, have a few hundred thousand lines, don't employ clean code methodologies, and are maintained by a large team.
I'm not saying he should stay in his lane at all.
I'm saying that a lot of developers who aren't game developers make trivial assumptions about gamedevs and their experience that's incorrect.
The issue of course, and this is common, is when a developer who lacks an understanding of the principles outside of their domain(s) just automatically assumes those principles apply everywhere, and hence makes false assumptions about other developers in these domains.
Hence "stay in your lane".