all 11 comments

sorted by: hot top controversial new old
[–] 29 points 5 months ago (3 children)

"A little copying is better than a little dependency."

  • source
  • hideshow 3 child comments
  • [–] 20 points 5 months ago (2 children)

    Judgement call. When it's something prone to change that's hard to get right, duplicating it just creates more maintenance burden.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 months ago

    Plus, it's bloat. A snippet of extra code isn't going to cause much trouble, but then you end up doing it a lot, and there's snippets in the snippets, and all the sudden something that used to fit on a floppy is 3 gigs.

    I have no idea how much of a factor this is relative other various performance-sacrificing shortcuts, but Wirth's law is a thing.

  • source
  • parent
  • [–] 11 points 5 months ago

    Depend on abstractions. This isn't hard. 🤷

  • source
  • [–] 3 points 5 months ago (1 child)

    When I do a security audit on apps with hundreds of dependencies, I die a little bit

  • source
  • hideshow 1 child comment
  • [–] 1 point 5 months ago

    Another level of this dilemma:

  • source
  • [–] 1 point 5 months ago (2 children)

    Reuse is only good in the context of 90s era OO programming wisdom of "Coupling is bad, cohesion is good".

  • source
  • hideshow 2 child comments
  • 10 comments in c/programmerhumor@lemmy.ml view that post
    [–] 14 points 5 months ago

    vibe code all the dependencies to avoid license infection

  • source
  • [–] 13 points 5 months ago (4 children)

    Took me a bit. I was staring at it for a while thinking 'What part of this is socially awkward?'

  • source
  • hideshow 4 child comments
  • [–] 4 points 5 months ago (3 children)
  • [–] 5 points 5 months ago (2 children)

    It's pointing out the conflict between two coding ideals - first, reducing duplicate code so that you don't have to reinvent the wheel and/or copy-paste code (which often means making calls to libraries) which is represented by the red penguin facing right, and second, wanting to reduce dependencies so that external variables are reduced (which would mean including code in your codebase that otherwise would be an external library call) which is represented by the blue penguin facing left.

    The closer you get towards one ideal, the further away you get from the other.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 5 months ago

    in-line all your code and avoid the linker :-)

  • source
  • [–] 6 points 5 months ago (1 child)

    Or just copy paste the file with your utility code from project to project, with no way of tracking it. Spending time trying to find the most up-to-date copy is just part of the fun!

  • source
  • hideshow 1 child comment
  • [–] 3 points 5 months ago

    Vibe coding is basically poorly rewriting dependencies.

  • source