• Vector@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    Standard shitpost and then out of nowhere “Hello inject me with beans please”

    WHY IS IT SO FUNNY

    • wer2@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      I inject myself with beans every morning, usually French press

  • davidgro@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    2 months ago

    I think this might be the first of these I’ve seen where pretty much all the comments are just agreement.

  • deadbeef79000@lemmy.nz
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    Urgh. I just sicked in my mouth.

    Die in a hole DI frameworks.

    I already have an injection ‘framework’ it’s called a constructor. I already have a factory it’s called new

  • koncertejo@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    As an audio engineer, I was very confused about what this had to do with Direct Injection for a second.

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

    We’re struggling to deal with climate change and these selfish developers can think of nothing except building more factories. This is a global issue, we need a global solution: eschew factories and services for defining everything globally.

  • MajorHavoc@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    I’ll never plaster the back of my car with stickers that all proclaim the same things in ALL CAPS.

    But if I was going to…

    It would pretty much match this meme.

  • cAUzapNEAGLb@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    I fucking hate Spring.

    The quickest way to get a team of 10 contractors to turn 100 lines of basic code from a decent engineer into 2k, with 50 janky vulnerable dependencies, that needs to be babied with customized ide’s and multi-minute+ build times and 60m long recorded meetings.

    Fuck Spring.

    • MajorHavoc@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Fuck Spring.

      Actually, there’s a lot to be said for being able to configure your spleamtomoter without needing to reverse the polarity on the stack cache rotator arm.

      I’m kidding.

      Fuck Spring.

    • passepartout@feddit.de
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      edit-2
      2 months ago

      Wouldn’t want to write a webserver / database connection / scheduler / etc. from scratch. Spring Boot plus lombok turns 2k lines of code into 100.

      • expr@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        Sure… That"s what libraries are for. No one hand-rolls that stuff. You can do all of that just fine (and, actually, in a lot less code, mostly because Java is so fucking verbose) without using the nightmare that is Spring.

  • Mikina@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    My favourite take on DI is this set of articles from like 12 years ago, written by a guy who has written the first DI framework for Unity, on which are the currently popular ones, such as Zenject, based on.

    The first two articles are pretty basic, explaining his reasoning and why it’s such a cool concept and way forward.

    Then, there’s this update:

    Followed by more articles about why he thinks it was a mistake, and he no longer recommends or uses DI in Unity in favor of manual dependency injection. And I kind of agree - his main reasoning is that it’s really easy for unnecessary dependencies to sneak up into your code-base, since it’s really easy to just write another [Inject] without a second thought and be done with it.

    However, with manual dependency injection through constructor parameters, you will take a step back when you’re adding 11th parameter to the constructor, and will take a moment to think whether there’s really no other better way. Of course, this should not be an relevant issue with experienced programmers, but it’s not as inherently obvious you’re doing something potentially wrong, when you just add another [Inject], when compared to adding another constructor parameter.

    • Doc Avid Mornington@midwest.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Exactly. Dependency injection is good; if you need a framework to do it, you’re probably doing it wrong; if your framework is too magical, you’re probably not even doing it at all anymore.

  • tatterdemalion@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Say what you want about DI frameworks, but if I have to remove another fucking global variable so I can write a test, I’m going to cut a bitch.

    • cadekat@pawb.social
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      Dependency injection is so much worse. Oh, hey, where’d this value come from? Giant blob of opaque reflection code.

      • Zagorath@aussie.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        It can be used in bad ways, but if it’s used in the right way you should never have the situation you just described.

        • cadekat@pawb.social
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          I’m not exactly sure what you mean. Doesn’t all dependency injection work the way I described?

          Without being familiar with the framework, you can’t trace your way from the class getting injected into to the configuration, even if you’re experienced with the language.

          • Zagorath@aussie.zone
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 months ago

            I don’t think so. When I’ve seen it done it’s usually not been random values injected (except when those values are secret keys which should absolutely not be stored in code to begin with), it’s usually injecting a service. Another class, usually with a name that makes it easy to trace down. Like if you’re building an OrderService, that might take as a dependency an IProductService, which would have injected into it the class ProductService (personally, I don’t like the Hungarian notation that C# uses, but it’s a convention and my preference for sticking to strong conventions for the sake of consistency outweighs my distaste for Hungarian notation). That’s easy to find, and in fact your IDE can probably take you straight to it from the OrderService’s constructor.