• lad@programming.dev
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    4
    ·
    3 months ago

    So, every time I use a library to recognize patterns on a picture, to interact with Kafka, do some SSL, or do database mapping, I should hate myself, noted

    We did Elastic API integration in Java by creating and maintaining huge half-codegenerated transformer from code to Elasticsearch’s JSONs, it was a pain and it was source of more than one error

    Dependences should be reviewed and audited to make sure they do what you need and they are worth using. Just making everything in-house gets you nowhere most of the time

    • aaro@lemmy.world
      link
      fedilink
      arrow-up
      23
      ·
      3 months ago

      Nobody is arguing that you should never depend on anything and create everything yourself, but adding a dependency for literally a one liner function is awful. Like one of the Go proverbs goes, a little copying is better than a little dependency.

      • lad@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 months ago

        Yeah, there’s mention of doing the opposite in C++ community in a neighbouring thread

    • JackbyDev@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 months ago

      That is what they were getting at by some self flagellation can’t hurt either. That sometimes “hating yourself” (adding dependencies) is worth it.

      • lad@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        3 months ago

        I read it as “also throw in some physical pain cause just feeling bad is not quite enough” 🤔