• idunnololz@lemmy.world
    link
    fedilink
    arrow-up
    82
    arrow-down
    1
    ·
    1 year ago

    Just create a global object and stuff your variable in there. Now you have a global singleton and that’s not a purely bad practice :D

        • SkyNTP
          link
          fedilink
          arrow-up
          40
          ·
          edit-2
          1 year ago

          Software dev is full of obscure keywords that describe otherwise pretty simple or basic concepts you stumble upon in practice naturally and that you probably already understand.

          • singleton: a class/object that is designed to be single use, i.e. only ever instantiated with a single instance. Typically used when you use class/objects more for flow control or to represent the state of the program itself, rather than using it to represent data
          • immutable: read-only, i.e. unchangeable
          • dependency injection: basically when you pass a function or object into another function object, thereby extending their effective functionality, typically for modular code and to separate concerns.

          Here’s one more of my favourite examples of such a keyword: memoization

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

      Real enterprise programmers know that everything should be on the stack… so they declare a List《void*》 in main.

      • idunnololz@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        1 year ago

        But we might need to add more features in the future so it might not just be a list in a few years. Better encapsulate it in a few layers of abstractions just to be safe.

    • z3rOR0ne
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      Ah yes. Global Objects, AKA the thinnest of condoms, lol.