This feels less like “Lisp is useful for devops” than “Here are three devops tools that use Lisp”. My area knowledge isn’t that great, but I’ve never heard of any of these three, so I assume they aren’t terribly common. If one is likely to find different, non-Lisp tools solving the same problems in the wild, and there’s no killer advantage to using these Lisp-based tools, then it doesn’t seem to me that the existence of these tools actually makes it true that Lisp is useful for devops.
I suspect that the author was more interested in sharing Lisp and these tools than making a specific claim about the relative utility of Lisp to a devops engineer, so I’m being overly nitpicky. But the post would be more compelling with at least a paragraph offering some advantages Lisp might have for devops, like the utility of declarative or functional languages for configuration. The lone comment on the post mentions Guix, which I have heard of, and which does press those specific advantages.
If you’re looking for article ideas, I would love to see an article that takes a standard and realistic Chef / Puppet / Docker setup and is fully replaced by bass. I think that might make it easier to get behind.
I’d say the will of the creator to make it feel more like a scripting language. At the time I first encountered it, it seemed promising enough for some stuff, but I never got the chance to test it in production.
It’s interesting how this doesn’t include guix which is configured wholly in guile scheme. You can create containers, virtual machines, packages, and systems all in scheme as well as deploy them to remote servers. It’s all encompassing sure but it’s still what I would consider the best option if you had to do DevOps in lisp.
This feels less like “Lisp is useful for devops” than “Here are three devops tools that use Lisp”. My area knowledge isn’t that great, but I’ve never heard of any of these three, so I assume they aren’t terribly common. If one is likely to find different, non-Lisp tools solving the same problems in the wild, and there’s no killer advantage to using these Lisp-based tools, then it doesn’t seem to me that the existence of these tools actually makes it true that Lisp is useful for devops.
I suspect that the author was more interested in sharing Lisp and these tools than making a specific claim about the relative utility of Lisp to a devops engineer, so I’m being overly nitpicky. But the post would be more compelling with at least a paragraph offering some advantages Lisp might have for devops, like the utility of declarative or functional languages for configuration. The lone comment on the post mentions Guix, which I have heard of, and which does press those specific advantages.
Great feedback, thank you!
If you’re looking for article ideas, I would love to see an article that takes a standard and realistic Chef / Puppet / Docker setup and is fully replaced by bass. I think that might make it easier to get behind.
Definitely seconded, plaze halp.
And a fourth tool: newLISP
Please don’t use newlisp for anything, ever.
Why not? Is it because it hasn’t seen a new release for a while?
What makes newLISP well suited for dev ops tasks?
I’d say the will of the creator to make it feel more like a scripting language. At the time I first encountered it, it seemed promising enough for some stuff, but I never got the chance to test it in production.
I use it all the time. newlisp is fun. It feels like LISP that has the good stuff from Perl and C and shell scripting pulled into it.
It’s interesting how this doesn’t include guix which is configured wholly in guile scheme. You can create containers, virtual machines, packages, and systems all in scheme as well as deploy them to remote servers. It’s all encompassing sure but it’s still what I would consider the best option if you had to do DevOps in lisp.
More advanced than cl-adams, Consfigurator: https://github.com/spwhitton/consfigurator