libmem_cpy-strnrrn-std-clib_Cmvaeffc_ld-TWA_nif.aarch64(32bit)2-0.13.2-23.2.so.7(3).1.1.gz.conf

Comments

• db2@sopuli.xyz ⁨8⁩ ⁨months⁩ ago

  aarch64(32bit)

  🤣

  source

  • bdesk@kbin.social ⁨8⁩ ⁨months⁩ ago

    He was using (a)arch

    source

    • H2207@lemmy.world ⁨8⁩ ⁨months⁩ ago

      Just the 1 premium linux distro please…

      source
  • H2207@lemmy.world ⁨8⁩ ⁨months⁩ ago

    x86 backwards compatibility

    source
  • Cyberflunk@lemmy.world ⁨8⁩ ⁨months⁩ ago

    Commodore 64 effective

    source
• bleistift2@feddit.de ⁨8⁩ ⁨months⁩ ago

  itoa, atoi

  source
• words_number@programming.dev ⁨8⁩ ⁨months⁩ ago

  Seriously though, why? Is there historic reasons for that? Did they have to pay extra for more letters back in the day?

  source

  • scurry@lemmy.world ⁨8⁩ ⁨months⁩ ago

    Yes. Memory and storage were at a very high premium until the 1990s, and when C was first being developed, it wasn’t uncommon for computers to output to printers (that’s why print() and co are named what they are), so every character was at a premium. In the latter case, you were literally paying in ink and paper by the character. These contributed to this convention that we’re still stuck with today in C.

    source

    • zqwzzle@lemmy.ca ⁨8⁩ ⁨months⁩ ago

      IIRC older DOS versions were also limited to 8.3 filenames, so even filenames had a max limit of 8 characters + 3 extension. May it was a limitation of the file system, can’t quite remember.

      source

      • -> View More Comments
    • words_number@programming.dev ⁨8⁩ ⁨months⁩ ago

      Thanks for the insight! I think this kind of convention that once made some sense, is now exclusively harmful, but is still followed meticulously, is often called “tradition” and is one of the high speed engines that let humanity drive towards extinction.

      source

      • -> View More Comments
    • QuazarOmega@lemy.lol ⁨8⁩ ⁨months⁩ ago

      Wait, but they didn’t print out the source code right? Or did they use teletypes to develop?

      source

      • -> View More Comments
  • mustardman@discuss.tchncs.de ⁨8⁩ ⁨months⁩ ago

    I worked with a complier that would assume only compare the first 8 characters and would treat it the same afterwards.

    Compiler copyright was around 1990.

    source
  • nothacking@discuss.tchncs.de ⁨8⁩ ⁨months⁩ ago

    They did, with core you could be paying for many dollars per bit of memory.

    source
  • NateSwift@beehaw.org ⁨8⁩ ⁨months⁩ ago

    I’ve heard arguments that back in ye old days each row only had 80 characters and variable names were shortened so you didn’t have to scroll the page back and forth

    source

    • Knusper@feddit.de ⁨8⁩ ⁨months⁩ ago

      I’ve already felt like I should choose shorter names in a (shitty) project where the customer asked us to use an auto-formatter and a max line-width of 120 characters.

      Because ultimately, I choose expressive variable names for readability. But an auto-formatter gladly fucks up your readability, breaking your line at some random ass point, unless your line does not need to be broken up.

      And so you start negotiating whether you really need certain information in a variable name for the price of badly broken lines.

      source

      • -> View More Comments
  • AngryCommieKender@lemmy.world ⁨8⁩ ⁨months⁩ ago

    We were limited to a certain number of characters for filenames, way back in the Apple ]|[ days. IIRC it was 8

    source