cross-posted from: https://feddit.de/post/7998742

Meme transcription: 4 panels of Vince McMahon reacting increasingly ecstaticly to:

  1. Your software isn’t working. Vince McMahon looks curious.
  2. The bug is in a library. McMahon smiles.
  3. There already is an issue on Github. McMahon makes an orgiastic face.
  4. They published a fix last week. [I don’t know how to describe the face McMahon is making.]
  • Pyro@lemmy.worldEnglish
    24·
    10 months ago

    I would say finding that the bug is in a library is worse than finding it in your own code.

    If it’s your own code, you just fix it.

    If it’s in a library you then have to go and search for issues. If there isn’t one, you then go and spend time making one and potentially preparing a minimum reproducible example. Or if you don’t do that (or it’s just unmaintained) then you have to consider downgrading to a version that doesn’t have the bug and potentially losing functionality, or even switching to another library entirely and consequently rewriting all your code that used the old one to work with the new one.

    Yeah, I’d take my own bugs over library bugs any day.

    • DefederateLemmyMl@feddit.nlEnglish
      7·
      10 months ago

      If there isn’t one

      Worse is if there is one but it says: [OPEN] Opened 7 years ago Updated 2 days ago, with a whole bunch of people commenting the equivalent of “me too”, and various things they tried to solve it, but no solution.

    • bleistift2@feddit.deOPEnglish
      2·
      10 months ago

      That’s where my ecosystem shines, since it’s all open source. If there’s a bug that I can fix, but the maintainer won’t, I’ll just fork the repo.