• Pissmidget@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    5 days ago

    When writing programming code, markup, or any other structured text of that sort, it is easier on the eyes and to parse mentally when vertically and horizontally aligned. At least when reading English characters left to right, top to bottom. (I don’t read much else in that capacity).

    Whereas with the written word, letters flow into each other, to give a better reading experience.

    As for ligatures, having != (not equal), <= (smaller or equal to), == (equal), === (extra certain we’re equal as we messed up the implementation of ==, but need backwards compatibility) or similar operators show as the symbols they represent (while still maintaining the correct spacing), is more comfortable when ingesting large amounts of code, to me at least.

    • A_norny_mousse@piefed.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      5 days ago

      ligatures, having != (not equal), <= (smaller or equal to), == (equal),

      Oh yeah I forgot about those. Those make perfect sense in a coding font, but I have seen “fi” or “ff” etc. together in 1 character cell and it’s completely unusable.

      • Pissmidget@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        5 days ago

        I haven’t experienced that myself, closest would be the Norwegian æ, but that is its separate letter on the keyboard, like ø and å. I can see why it’d be awful in some contexts though.

        • A_norny_mousse@piefed.zip
          link
          fedilink
          English
          arrow-up
          3
          ·
          5 days ago

          It happened a few years ago and I’m not keen on repeating the experience just to analyse it further … soon even I won’t remember it anymore