• FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    5 months ago

    I haven’t ever used Ansible but I have used a project that also made the boneheaded decision to use templated YAML. That cost me several hours of debugging…

    This is goes with the previous point, and this is a subjective argument too: if YAML is enough for a task, there is no price to pay, at any time; if YAML is not enough, there has been a miscalculation during the tool choice.

    Well, yeah I think he’s saying that Ansible is the wrong tool and he’s making a better one. It’s also not just that YAML isn’t “enough for a task”. It’s extremely error-prone and add unhygienic templates onto an already janky language is just asking for trouble.

    most of development reasons seem straw man arguments … I have some counter-arguments

    Tbf you agreed with half the points you quoted…

    I think the biggest problem with this replacement is the choice of Raku. That’s a super niche and quite weird language that nobody is going to want to learn. I would have probably used Typescript or maybe Dart.

    • asperan@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      Well, yeah I think he’s saying that Ansible is the wrong tool and he’s making a better one. It’s also not just that YAML isn’t “enough for a task”. It’s extremely error-prone and add unhygienic templates onto an already janky language is just asking for trouble.

      Fair enough, I guess I have never had to use Ansible for big enough projects where these kinds of error spring up more frequently.

      Tbf you agreed with half the points you quoted…

      Well, the only one that I agree completely with is the stdout/stderr one. All the others have some kind of caveat that prevents me to support OP claims.

      In any case, on the language choice we are in agreement: as of now Raku is not a popular language, so requiring a user of the system to know the language cannot provide much appeal to the project.

      • Elizabeth Mattijsen@programming.devOPM
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 months ago

        In any case, on the language choice we are in agreement: as of now Raku is not a popular language, so requiring a user of the system to know the language cannot provide much appeal to the project.

        FWIW, for this application, I’d say only knowledge of “baby” Raku is needed. And if you’ve had any exposure to “baby” Perl in the past, then you already have that.

        • FizzyOrange@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          5 months ago

          Yeah I mean I knew Perl back in the 90s. I’m not super keen to relearn it just for this. Why not use a more mainstream language?

          (I’m guessing the answer is “because I made this for me, and I want to try Raku” or something, which is fine.)