A lot of the discussion on this post ended up being about LessWrong norms. I've moved that particular thread over to the comments here, and left a comment there pointing over here.
(Some of those comments, including the initial one, were object-level relevant to this post. I apologize for moving all of them indiscriminately. Our comment-moving-features are a bit janky and it's easier to move an entire thread than individual subthreads. I also apologize for breaking a lot of the comment-permalinks in that thread, and we'll look into fixing those. Meanwhile, you can actually still hover-over the comments in question on LW to see a preview of the comment, and you can also copy the comment-hash from the link and apply it to the new post to get a working link)
I have this intuitive notion that:
When people talk about "demanding" in this sense what they're actually doing is a very low level reasoning mistake EY talks about in his post on Security Mindset:
Where, there is a certain level of detail and effort that simply has to go into describing concepts if you want to do so clearly and reliably. There are inviolable, non-negotiable laws of communication. We may not be able to precisely define them but that doesn't mean they don't exist. We certainly know some of their theoretical aspects thanks to scholars like Shannon.
I think a lot of what Said does is insist that people put in that effort, that The Law be followed so to speak. Unfortunately there is no intrinsic punishment for not following the law besides being misunderstood (which isn't really so costly to the speaker, and hard for them to detect in a blog format). That means they commit a map/territory error analogous to the Rust programmer who insists Rust makes things much harder than C does. There's probably some truth to this, but a lot of the thing is just that Rust forces the programmer to write code at the level of difficulty it would have if C didn't let you get away with things being broken.