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.
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.
Fair enough, I guess I have never had to use Ansible for big enough projects where these kinds of error spring up more frequently.
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.
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.
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.)