The sentence has exactly same meaning if they'd use a single "-" as well. I don't know which browsers have <textarea>s where double "--" is turned into emdash, but on the systems I'm familiar with one needs to go certain lengths before an emdash appears.
Emdash does not magically appear, and it seems some people love playing with the AI connotation.
On mobile it's long-press the hyphen on the keyboard.
On Windows I use https://cemrajc.github.io/em-n-en/ so that ==- is turned into it system-wide.
On recent Ubuntu versions, you can set up Compose Key, for example with Caps Lock: https://www.danielkossmann.com/how-to-get-em-dash-ubuntu-lin...
I've long been an em-dash user and enjoyer and hope that using it stops becoming such a signal for AI text.
See also: <https://chrismorgan.info/.XCompose>, <https://chrismorgan.info/ai>.
You will find more than a few here on HN that type what they want rather than what standard keyboards make easiest.
Setting an em-dash used for parentheticals closed (with no space)—or sometimes with thin spaces—is the common American literary/academic style (Chicago Manual, APA, and MLA all prefer closed); setting it open—with full word spaces—is the common American practice in journalism (reflected in the AP style guide). Not using em-dash at all for that use, but instead using an en-dash set open is the common British practice.
Even for Americans, there are several style guidelines/modern preferences (particularly around web content) which don't guarantee the lack of spaces around an em dash. Hence even American LLMs using spaces. Ecen my natural em dash usage always included spaces as an American.
When I go to print, I use hairspace, but it’s not worth the trouble in comments.
I’m not sure I agree with using length as the metric to decide which style guide is more appropriate for comments. I’d rather follow one consistent style in general than change it depending on the type of content I’m writing.
Still, good point on the style guides targeting specific usages.
I used to love Linux's compose keys, though, where I could just press `<win>--.` to get an en dash and `<win>---` to get an em. Most of the compose combinations were guessable, like `<win>a'` for á, `<win>co` for ©.
MacOS has a great keyboard locale switcher, but the lack of real compose keys limits things. Most characters you can press and hold and get some accented versions, but it's very slow if you're typing in French or something in the EN layout. It also has a built-in character picker, which is really nice but even more slow.
Just wait until I decide to go all in on TWO-EM DASH⸺I have thought for a long time that EM DASH isn’t wide enough. Or maybe THREE-EM DASH⸻though it’s normally too wide. But alas, font support isn’t good on these so you might get bad alignment or line-height inconsistency; and I might end up wanting to surround it with THIN SPACE or HAIR SPACE, and HN mangles exotic spaces to just SPACE. :-(
(Honestly, my original comment would be improved by using TWO-EM DASH, or maybe even THREE-EM.)
You know, there are more than two possible choices. I scorn to subject myself to any style guide for my personal writing… let alone an American one. People used em-dash-sans-space long before CMOS was dreamed up.
I sha’n’t follow all the older traditions I find, but I do frequently favour them.
The GP’s post history suggests they have some touch with typography.
Please face it: especially on a site like HN, you will encounter em dashes from real humans, whether converted by some system software or typed deliberately.
Em dashes are a weak signal at best. On HN, they’re a very weak signal.