“No Duh,” say senior developers everywhere.

The article explains that vibe code often is close, but not quite, functional, requiring developers to go in and find where the problems are - resulting in a net slowdown of development rather than productivity gains.

  • Rose@slrpnk.net
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 hours ago

    Oh yes. The Great pathlib. The Blessed pathlib. Hallowed be it and all it does.

    I’m a Ruby girl. A couple of years ago I was super worried about my decision to finally start learning Python seriously. But once I ran into pathlib, I knew for sure that everything will be fine. Take an everyday headache problem. Solve it forever. Boom. This is how standard libraries should be designed.

    • namingthingsiseasy@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      Pathlib is very nice indeed, but I can understand why a lot of languages don’t do similar things. There are major challenges implementing something like that. Cross-platform functionality is a big one, for example. File permissions between Unix systems and Windows do not map perfectly from one system to another which can be a maintenance burden.

      But I do agree. As a user, it feels great to have. And yes, also in general, the things Python does with its standard library are definitely the way things should be done, from a user’s point of view at least.

    • HugeNerd@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      4 hours ago

      I disagree. Take a routine problem and invent a new language for it. Then split it into various incompatible dialects, and make sure in all cases it requires computing power that no one really has.