• Hazzard@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      41 minutes ago

      As much as I think that’s correct a lot of the time, something like Bruno has value too. Implementing complicated auth for an annoying service once and reusing it across several pre-written requests, useful features like a GUI and history to see prior responses from an endpoint, being able to share the “collection” in the repo as examples/developer tools that’s maintained alongside the code, writing docs with each request to explain its usage, this stuff does add value that isn’t trivial to do with curl.

    • lmr0x61@lemmy.ml
      link
      fedilink
      English
      arrow-up
      40
      arrow-down
      1
      ·
      20 hours ago

      This has been solved since 1999. Read the manual.

      The deeper I get into Linux, the more I feel exactly this about most software in general. We just love reinventing the wheel, don’t we?

      • Thorry@feddit.org
        link
        fedilink
        arrow-up
        22
        ·
        17 hours ago

        I have been working as a professional in the dev space for over 25 years. I have contributed to developing the same software over a dozen times, some even at the same company. Over time the tools have changed, the people have changed and my role has changed. But the overall specs have remained very similar if not the exact same.

        Recently I did a job for a company where I was a consultant on a large project, they specifically sought me out for my expertise in the subject matter (having been involved in many similar projects). One of the C suites left the company near the end of the project, no reason given. This week he contacted me, he is now a C suite at another big company. They want to do the exact same project and want to hire me because of my expertise. I laughed my ass off, but am very happy with the work and he is a good guy (as far as C suites can be at least).

        • lmr0x61@lemmy.ml
          link
          fedilink
          English
          arrow-up
          7
          ·
          16 hours ago

          That’s a great story lmao So it’s DRY… unless you’re getting paid to do it? 😂

      • chunkystyles@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 hours ago

        I installed it yesterday, and the biggest issue I’m having is envisioning what a mature project would look like in it. I have not gone looking for examples like that, but if you know of any, i’d love to see some.

        • nikolasdimi@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          ·
          1 hour ago

          hey - thats great :) Happy you downloaded it :) curious to hear your feedback - I will send you a discord link as a message so its not seen as spamming.

          Let me see if I understand your question: you mean how Voiden would look when its more mature?

          What I am most excited about is that Voiden already does a few things differently from most API tools. Reusable blocks, plain-text everything, and the ability to go from testing to docs to publishing from a single source are already working and shaping how teams can work in a more consistent way.

          There is still a lot ahead (for example I want to see what kind of plugins people come up with for the tool, or how AI will eventually play a bigger role) but the principles of Voiden (reusability, composability, plain text, collaboration through git, single source of truth etc.) are the ideas I believe will define and set a new tone/standard of how API tools should be.

  • vpol@feddit.uk
    link
    fedilink
    arrow-up
    18
    ·
    20 hours ago

    Same thing with every single tool. 90% of posts have hidden promotion. If not direct, then in the comments OP will “recommend”. If not in the comments - they are playing long game and wait to gain trust.