3 ms·
Because before giving lessons to others you should be irreproachable. What would you think of Dijkstra if you suddenly discovered that he still wrote goto infe
by jmnicolas 6y ago
Because before giving lessons to others you should be irreproachable.
What would you think of Dijkstra if you suddenly discovered that he still wrote goto infested spaghetti code after his notorious "Go To Statement Considered Harmful" paper ?
So yes we should criticize China as the bad actor that it is, but let's not forget that the western world is hardly an example (a good one I mean ;)
- klyrs 6y agoUnderneath any high-level programming language is a layer of goto-infested spaghetti code. Dijkstra lost the stomach for low level optimization and convinced generations of programmers that easy is better than efficient.
- jmnicolas 6y agoI think you missed my point : it was about hypocrisy not about gotos ;) Anyway in my usecase, easy is better than efficient : I'm in my 12th year of coding desktop and backend apps in C# and my first time having to rethink my code because it was too slow was only last year where I had to use dictionaries instead of Linq for a project that manipulates a lot of data (yes using dictionaries instead of Linq is the extent of my "optimization" and it's enough). In those 12 years I never thought "if only I had a lower level, more efficient language than C#" (quite the opposite in fact). So IMO it all depends on what you do : of course if your code is deployed to something less powerful than an Arduino I understand that efficiency is paramount !