• Feathercrown@lemmy.worldEnglish
        2·
        2 months ago

        GNU’s Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix CORE DUMP: OUT OF MEMORY EXCEPTION

  • toastal@lemmy.mlOP
    0·
    2 months ago

    Acronyms/intialism use capital letters to encode information about words. Losing that information is a mistake. SᴍᴀʟʟCᴀᴘCᴀsᴇ is now considered a best practice.

    …Or I dunno try snake_case or kebab-case 🤷

  • Boomkop3@reddthat.com
    0·
    2 months ago

    I don’t like to sticking to generalized naming conventions when autofill or intellisense is a thing. Make your names clear in whatever way you think works best, and developers still using vim can set up autocomplete using an extension or something

    • Kraiden@kbin.run
      1·
      2 months ago

      Dear god please no. This way madness lies. Your idea of “whatever you think works best” is not going to line up with whatever the next person that comes along thinks, and your codebase is about to get all kinds of fucked up.

      Thinking code complete is going to save you is naive. Even in languages like C and Java, where it works best, you still need to be able to read and understand the code in context. There’s no hope in a language like Ruby with all it’s meta programming stuff