Reply to thread

Message

<blockquote data-quote="Oofta" data-source="post: 8258652" data-attributes="member: 6801845">Rules as a technical document was one of the things they went out of their way to avoid.&nbsp; First, it never really works. The more detailed rules you have, the more exceptions you have, the more exceptions and clarifications you have the more you need. It's a never ending rabbit hole.The other thing is that geek speak is a huge barrier to a lot of people.&nbsp; Some of the previous editions were full of it, and it raised a pretty high perceived barrier to entry.&nbsp; The rules are far from perfect, but writing them as a technical manual would have only made it worse.&nbsp; That, and we'd still find problems.&nbsp; <img class="smilie smilie--emoji" alt="🤷‍♂️" src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f937-2642.png" title="Man shrugging&nbsp; &nbsp; :man_shrugging:" data-shortname=":man_shrugging:" loading="lazy" width="64" height="64" /></blockquote>

[QUOTE="Oofta, post: 8258652, member: 6801845"] Rules as a technical document was one of the things they went out of their way to avoid. First, it never really works. The more detailed rules you have, the more exceptions you have, the more exceptions and clarifications you have the more you need. It's a never ending rabbit hole. The other thing is that geek speak is a huge barrier to a lot of people. Some of the previous editions were full of it, and it raised a pretty high perceived barrier to entry. The rules are far from perfect, but writing them as a technical manual would have only made it worse. That, and we'd still find problems. 🤷‍♂️ [/QUOTE]

Verification