image saying "at least the important software isn't being vibe cod-" (cut off) and showing a graph of em dashes in the linux kernel over time with a sharp rise the past few years
you are viewing a single comment's thread
view the rest of the comments
[–] 30 points 4 days ago (20 children)

What is the accelerating rise of m-dashes from approximately 2014-2019 about? That trend apparently continued until very recently, even slowed down a bit, before exploding at some point in 2025 or 2026 for obvious reasons.

Does anyone have a theory?

  • source
  • hideshow 20 child comments
  • [–] 18 points 3 days ago (3 children)

    If the graph is not just using made up data, then it also measures absolute em-dashes, not em-dash density, so possibly could be an increase in interest in contributing to the kernel?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 3 days ago* (2 children)

    By a factor of roughly 10-fold? Maybe. It could indeed be a measure of overal absolute contribution. But post 2025 that could be influenced by m-dash density especially.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 3 days ago (1 child)

    The OP graph is just absolute count on the y axis, so I also assumed it was basically measuring LoC, but looking at this chart, the em-dashes do appear to be definitely more of a modern phenomenon compared to raw LoC:

    Maybe some policy/tooling change around 2014? A guess is perhaps something to do with allowing UTF-8 in source files, but that's a pretty long shot.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 3 days ago (8 children)

    I wonder how many em dashes are real vs interpreted.

    I love an em-dash, but I have never typed one on purpose; they are all just two minus in a row and I use them wrong -- with a space around (*inspect source to see that lemmy translates for me). I abuse them like I abuse semicolons. They are a typographical tick that indicates a pause or pivot when I translate my thoughts to text.

    I can imagine a human manuscript editor turning punctuation like a comma into an em-dash when it makes sense, but I can't imagine a developer ever specifically typing out one -- with the need to either know or look up the unicode for it. The only relevant place would be a comment, but even then IDE's are not generally known for their tendency to replace typed characters with something else.

    Maybe some tool in the pretty-print/code-formatter ecosystem added that as a feature? But var-- is so common that I can't imagine that'd be a good idea, even in a comment.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 4 points 3 days ago (4 children)

    They probably write code in Microsoft Word

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 3 days ago (2 children)

    For pedantry's sake:

    Two dashes -- -- -- in Markdown is usually rendered as an en-dash -- more common in British-adjacent styles and usually surrounded by spaces.

    Three dashes---------in Markdown is rendered as an em-dash---more commonly associated with American styles and usually (though not always) without spaces.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 days ago (1 child)

    Hah. Neat!

    For pedantry...

    My understanding was that en-dash was a range, and em-dash was a change in topic or a parenthetical, so I've been using the wrong one but for the right reason. This may be an American style distinction, though. Time to jump into a new rabbit hole.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 days ago

    I've always just used a hyphen for ranges, without having any idea whether that makes me a philistine. A quick search says that, like most of this, it varies depending on who you ask.

    Good luck in your rabbit hole!

  • source
  • parent