• aidan@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    20 days ago

    I can’t relate to this feeling at all, writing code using a library I’ve found is almost always the source of bugs. Miscommunication between the library developer and their documentation, or my ability to read the documentation. And that’s on top of how many big libraries I’ve seen with extremely simple exploits. Sadly I have to use a few, but I wince every time I install a package.

    • Radioactive Butthole@reddthat.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      20 days ago

      I am NOT writing a database connector unless you add an additional three months to your projects expectations.

      I am NOT writing an LDAP connector.

      I am NOT writing code to execute shell processes safely.

      And I’m sure as hell not writing an XML parser just so I can say I did it without libraries.

      JS devs that import libraries for every stupid thing (lpad comes to mind) are bad programmers, but libraries are useful and have their place.

      And if my boss doesn’t want me using those libraries, they need to specify that in advance or there needs to be a company policy to that effect. Otherwise, I’m solving the problem my way since that’s what I’m getting paid to do.

      • aidan@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        17 days ago

        Yeah I absolutely agree, my issue is with libraries that do trivial or not particularly useful things.