3 ms·
>What's the problem you see with an interpreted language? Keeping the package up to date for odd systems like Illumos and BSDs. Most interpreted languages requ
by evanjrowley 2y ago
>What's the problem you see with an interpreted language?
Keeping the package up to date for odd systems like Illumos and BSDs. Most interpreted languages require a whole ecosystem and modules just to install. The one exception is shell script because it usually comes out of the box, but each of those platforms also has a different version too. That's why I'd prefer something statically compiled, which is typically antithetical to interpreted languages.
Comtrya seems like a cool solution, has BSD support, but it's in very early stages: https://comtrya.dev/introduction.html https://comtrya.dev/introduction.html
Remco also looks good, although it's also more complex: https://github.com/HeavyHorst/remco https://github.com/HeavyHorst/remco
NSH seems like an awesome solution, but it's only for OpenBSD: https://github.com/yellowman/nsh https://github.com/yellowman/nsh
- verdverm 2y agoWe only use a single operating system for the entire org, Rocky The point of something like ansible is to keep all machines in lockstep, so you don't end up with multiple versions. For anything developed on the machine, or developed to run on the machine, use containers or a python virtual environment. Then you don't get conflicts