You haven't given any argument otherwise, other than that you were inconvenienced by it. While I've given many counter examples.
There used to be a trend in blaming Microsoft for everything bad, and that it was intentional, rather than unforeseen. That's what this feels like.
In all honesty, I wish they would move ahead, and not take older Windows 3.1 16-bit applications into account when developing the file system. Not worry about legacy compatibility. Anything that can't handle spaces in the name in this day and age is either (a) old, or (b) not developed correctly.
Windows wouldn't be so much of a mish mash if they quit taking into account old legacy applications. But they don't.
But we do agree on something. If you can't look at the arguments and links I provided above, and see how it explains away the fact that they were using spaces to booby trap the file system, then nothing I say will convince you otherwise.