> Oh, how they dare argue with WALTER BRIGHT. The hubris!
With all due respect, but if someone says something invalid, the fact that they have authority on a subject does not mean that we should agree.
As far as I understand the article (And I'm not the great Walter Bright, so I may be wrong) - the author states that "void foo(char a[..])" is better syntax than "void foo(size_t s, char a[])" but does not provide any arguments for it. Furthermore, the author initially fails to mention that there has been an attempt to fix the array-to-pointer-decay issue, when discussing "C's Biggest Mistake".
So, yeah, the author may be right that this has been C's biggest mistake. I don't know whether that is true or not, I do not have his experience. It is certainly true that this mistake would be high on rankings of all mistakes that C did. Still, the initial "sleight of hand" move followed by unsubstantiated argument leads to a post with the quality similar to that of a twitter post. Maybe even worse, since, you know, it's posted on a place other than twitter, so we are actually talking about it as if it was something serious.
I don't think that you are correct. Well... maybe they do know it and are opting for an alternative approach, because guilt-tripping seems like a fairly common tactic, especially in the aforementioned activists.
I'm sorry, but how did you come to this conclusion? The first thing that comes to mind is the new tactic used by activist, saying something to the effect of "If you are not doing something to prevent racism, then you are guilty of being racist." Which is what (I believe) lead to this thing: https://www.businessinsider.com/white-protesters-confront-di...
With all due respect, but if someone says something invalid, the fact that they have authority on a subject does not mean that we should agree.
As far as I understand the article (And I'm not the great Walter Bright, so I may be wrong) - the author states that "void foo(char a[..])" is better syntax than "void foo(size_t s, char a[])" but does not provide any arguments for it. Furthermore, the author initially fails to mention that there has been an attempt to fix the array-to-pointer-decay issue, when discussing "C's Biggest Mistake".
So, yeah, the author may be right that this has been C's biggest mistake. I don't know whether that is true or not, I do not have his experience. It is certainly true that this mistake would be high on rankings of all mistakes that C did. Still, the initial "sleight of hand" move followed by unsubstantiated argument leads to a post with the quality similar to that of a twitter post. Maybe even worse, since, you know, it's posted on a place other than twitter, so we are actually talking about it as if it was something serious.