I wasn’t sure how to express my gratitude.

It wasn’t bad for the occasional topical jest but holy shit does it make reading feeds painful.

Edit: in no way am I making a statement about code syntax. We don’t write documentation in camel case for good reason.

  • palordrolap@kbin.social
    link
    fedilink
    arrow-up
    36
    ·
    1 year ago

    THEREareWORSEwaysTOtypeTHINGSandSTILLhaveTHEMbeKINDofREADABLE.whoNEEDSspacesWHENweHAVEtwoLETTERcases?

    OrMaYbEwEcOuLdEsChEwEvEnThAtAnDjUsTaLtErNaTe.IfThErEaReWrItInGsYsTeMsWiThOuTvOwElsThAtCaNsTiLlBeReAdWhYnOtWrItElIkEtHiSiNsTeAd?

      • Neshura@bookwormstory.social
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        I had to constantly skip back and forth to figure out where one word starts and another ends. Very painful to read, I’ve found new appreciation for whitespace.

        • xmunk@sh.itjust.works
          link
          fedilink
          arrow-up
          4
          ·
          1 year ago

          If you go back in time far enough you can find manuscripts from before word separators were standard… they fucking suck.

    • Hazzard@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Surprisingly legible, but feels like I can only read it with momentum, flitting past it and letting my subconscious tell me where the word breaks are. The moment I get confused and look more closely, it becomes almost impossible to read.

    • milicent_bystandr@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I’m surprised how easy that is to read!

      Sorry, am on mobile: snarkily replying in some weird letter mashup is far too much effort right now.