I’m guessing this list is defined by Mac users who all got taught em dash somewhere similar or for similar reasons. It is only easy to use on a Mac. But I wonder what is the 2nd common influence of users using it?
As per the wiki article someone else listed — the compose key was available on keyboards back in the 1980s (notably it was invented only 5 years after the Space Cadet keyboard was invented!).
Some DOS applications did have support for it. The reason it wasn't included is baffling, and it's especially baffling to me that other operating systems never adopted it, simply because
compose a '
is VASTLY more user friendly to type than:
alt-+
1F600
which I have met some windows users who memorize that combo for things like the copyright symbol (which is simply:)
The compose key feels mandatory for anyone who wants to type their native langauge on an US-english layout. The combination[0] is "Compose--." though: –
As it should be. I wish this convention were present across more software, “-“ “- -“ and “- - -“ should be the UI norm for entering proper dashes in text input controls.
Though it does still require nominating a key to map to Compose. And is not generally meaningfully documented. So I’d only call it easy for the sorts of people that care enough to find it.
But then, long before I had a Compose key, in my benighted days of using Windows, I figured out such codes as Alt+0151. 0150, 0151, 0153, 0169, 0176… a surprising number of them I still remember after not having typed them in a dozen years.
In electrical engineering I'm still using a few alt codes daily, like 248 (degree sign), 234 (Omega), 230 (mu), and 241 (plus or minus). I'd love to add 0151 to the repertoire, but I don't want people to think I used AI to write stuff....
My favourite android keyboard has a compose key and also a lot of good defaults in long touch on keys (including en and em under dash). Only downside is last android update causes the keyboard to be overlapped in landscape mode. A problem with a number of alternative keyboards out there.
https://github.com/klausw/hackerskeyboard/issues/957
And whether the user cares to ‘write properly’ to boot. I love using dashes to break up sentences - but I rarely take the time to use the proper dashes, unless I’m writing professionally. I treat capitalization the same way - I rarely capitalize the first letter of a paragraph. I treat ‘rules’ like that as typographic aesthetic design conventions - optional depending on context.
I recently learned to use Option + Shift + `-` (dash) on macOS to type it and use it since then because somebody smarter than me told me that this is the correct one to use (please correct them if you know better :D).
I've been typing "—" since middle school 25 years ago. It's trivial on a mac and always has been (at least since OSX, not sure about classic). Some folks are just too narrow-minded to give others the benefit of the doubt.
I'm a bit ashamed to say that, after using various ASCII symbols (for progress, checkmarks etc.) in the 90s and early 2000s, when I first discovered we can actually put special Unicode characters on the terminal and it will be rendered almost universally in a similar way, it was like discovering an unknown land.
While rockets and hearts seem more like unnecessary abuse, there are a few icons that really make sense in CLI and TUI programs, but now I'm hesitant to use them as then people who don't know me get suspicious it could be AI slop.
I don't love emojis for this purely because they're graphically inconsistent; I can't style them with my terminal font or colour scheme. But I'm a huge fan of using various (single-width) unicode chars with colour to make terminal output a lot easier to parse, visually. Colour and iconography are extremely useful.
It's the same thing as naming your servers Titan and Cerberus, using garish RGB LEDs on every computer part (in a glass case of course), and having a keyboard that looks like a disco.
The more vapid parts of social media also seem to have plenty of emoji floods, and I suspect that also made it into the training data for ChatGPT and others.
That's because utf-8 was such an absolute mess in JS that adding an emoji in your code was a flex that it worked.
Sane languages have much less of this problem but the damage was done by the cargo cultists.
Much like how curly braces in C are placed because back in the day you needed you punch card deck to be editable, but we got stuck with it even after we stared using screens.
> Much like how curly braces in C are placed because back in the day you needed you punch card deck to be editable, but we got stuck with it even after we stared using screens.
Can you expand on this? What do curly braces have anything to do with punch card decks being editable? What do screens?
I'm dubious of this explanation because C itself largely postdates punched cards as a major medium of data storage, and some quick searches doesn't produce any evidence of people using punch cards with C or Unix.
It was far before ChatGPT. I remember once on a Show HN post I commented something along the line with "The number of emoji in README makes it very hard for me to take this repo seriously" and my comment got (probably righteously) downvoted to dead.
I think I remember exactly what you're talking about, even though I completely forgot what software it was.
I believe it was a technical documentation and the author wanted to create visual associations with acteurs in the given example. Like clock for async process of ordering, (food -) order, Burger etc.
I don't remember if I commented on the issue myself, but I do remember that it reduced readability a lot - at least for me.