Comment on The temptation is always there

idunnololz@lemmy.world ⁨1⁩ ⁨year⁩ ago

• Techmaster@lemm.ee ⁨1⁩ ⁨year⁩ ago

  Just call it “state management” and nobody will even care.

  source
• magic_lobster_party@kbin.social ⁨1⁩ ⁨year⁩ ago

  Not necessarily a bad practice if the singleton is immutable, and it’s provided via dependency injection for example.

  source

  • wreckedcarzz@lemmy.world ⁨1⁩ ⁨year⁩ ago

    As a hobby coder: “mmmhm, mmmm, mmhm… I know some of these words!”

    source
• Anonymousllama@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Important to contain all your mess to one side of the room, makes it easier to manage

  source

  • shotgun_crab@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Yeah yeah let’s put all the eggs in one basket

    source
• mdk_@lemmy.world ⁨1⁩ ⁨year⁩ ago

  So you saying, just the tip?

  source
• xmunk@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

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

  source

  • manapropos@lemmy.basedcount.com ⁨1⁩ ⁨year⁩ ago

    Real enterprise programmers know you can get another job in the next year or two so fuck best practice

    source
  • idunnololz@lemmy.world ⁨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.

    source
• HurgletOfficial@lemmy.basedcount.com ⁨1⁩ ⁨year⁩ ago

  I do this all the time in Python by creating a class like

  class Core:
      foo = "bar"
  

  source

  • ryannathans@aussie.zone ⁨1⁩ ⁨year⁩ ago

    That’s not immutable nor a singleton

    source

    • xmunk@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      That makes it inherently multithread compatible!

      source