It is perfectly OK (it really is) to use parentheses -- and emdashes alike -- where they're useful; other punctuation like the semicolon, the comma, and even the Oxford comma are also OK.
There's not much that is disallowed in English. Most people have no reason to adhere to any particularly-rote style guide.
Parentheses add emphasis to a sentence or statement. Normally the use of it allows the sentence to be complete with or without it.
Em dashes may also add or increase emphasis but are normally treated as an aside. Think of it as a comment by the author to inject themselves, sometimes in ways which do not form a complete sentence.
For example: When you read this sentence (in your mind) it should feel complete and correct. Perhaps you read in your own voice — something I don’t normally do — or without one at all.
> I don't understand what the issue even is here, and the RFC also doesn't clearly outline it.
The issue is written there but may not make sense unless you know someone who stylistically writes with high-than-average em dash usage. I, for example, get inquiries and comments at work from employees who ask what LLM model I used for “generating these reports” because of the presence of em dashes. They do not believe me when I say not a single word was written by LLMs because, “there’s an em dash. Only LLMs use em dashes!” This is categorically untrue and erodes the authenticity of work from people because of the correlation.
Their aim is to implement a new Unicode character which programs like text editors could inject when a person types an em dash. It attributes to a human being behind the document, typing characters out individually. Actions like copy-pasting text in bulk wouldn’t replace em dashes since it can’t attribute a human as writing it out.
A semicolon is better for this purpose. Good writing doesn't have mad tangents anyway, there should be a flow and natural transition.
> For example: When you read this sentence (in your mind) it should feel complete and correct. Perhaps you read in your own voice — something I don’t normally do — or without one at all.
I would have used parentheses in both places, and semicolons don't work in either one:
> For example: When you read this sentence (in your mind) it should feel complete and correct. Perhaps you read in your own voice (something I don’t normally do) or without one at all.
Sure they do. They're perfect for a related tangent without abounding the greater scope topic being discussed.
> I would have used parentheses in both places, and semicolons don't work in either one:
Parentheses work no question and I would argue are far more appropriate in that example since it's a minor elaboration/clarification and not a tangent, indeed, semicolons would not be appropriate for that.
In general, yes. Technical documents, research reports, news articles, and other formal publications should follow this.
Anything else which allows a bit more freedom in expression? I’d say it’s a matter of taste.
"In regular prose, a semicolon is most commonly used between two independent clauses not joined by a conjunction to signal a closer connection between them than a period would." Chicago Manual of Style, 18th Edition, 407.
I use em-dash (written as "--" because I don't have an emdash key on my keyboard) as punctuation that sits between a semicolon and a period.
You can also just avoid the whole rigamarole and have a separate explanatory sentence.
Times change, good writers adapt.