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
      6·
      9 months ago

      THEREareWORSEwaysTOtypeTHINGSandSTILLhaveTHEMbeKINDofREADABLE.whoNEEDSspacesWHENweHAVEtwoLETTERcases?

      OrMaYbEwEcOuLdEsChEwEvEnThAtAnDjUsTaLtErNaTe.IfThErEaReWrItInGsYsTeMsWiThOuTvOwElsThAtCaNsTiLlBeReAdWhYnOtWrItElIkEtHiSiNsTeAd?

        • Neshura@bookwormstory.socialEnglish
          1·
          9 months 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.

      • Hazzard@lemm.ee
        0·
        9 months 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.

        • sjmulder@lemmy.sdf.org
          0·
          9 months ago

          Note that while Visual C++'s msvcrt doesn’t implement this POSIX function officially, there’s a nonstandard _ofcyfpos_s() and it will in fact warn you that any use of the official ofcyfpos() is unsafe. The semantics are slightly different (it’ll return 1 on success instead of the length of the reply) so you can’t just #define the problem away.

      • sjmulder@lemmy.sdf.org
        0·
        9 months ago

        Don’t forget to set the cbSize of the GETWITTYREPLYEXINFO structure before passing it to GetWittyReplyEx() or you’ll get funny things happening to your stack!

        • JoYo@lemmy.mlOPEnglish
          0·
          9 months ago

          You didn’t specify wide or ascii, we’re all doomed.

          I’m glad to to meet another Knight of 9x.