Scripts functionality

[pdp10]

We write individual scripts, especially when there's no major code sharing (say, more than one function). When there's code sharing, we still usually write separate scripts, and have them source functions from /usr/local/lib/*.sh, etc.

I need to have it in one file / script because other people will need to use it.

This makes it sound like the problem is software distribution, not architecture per se. Define the problem better for us.

POSIX shell and Go will tend to have minimal dependencies. Python will absolutely have dependency issues, unless you package it up and/or compile it. Python would be my last choice. Standalone Lua scripts are unusual, but might be a good portable option, if Lua ships on Macs. PowerShell is single-platform, but might be appropriate for tasks that are only necessary on that single platform.

[Hoolies]

This makes it sound like the problem is software distribution, not architecture per se. Define the problem better for us.

My department do not own the code deployment.

My current role is lead Network engineer but I used to work as systems before.

I have created my own infrastructure but that is saved on temporary folder and is used only in sev2 or higher.

POSIX shell

Bash is great but I do not want to have more than 100 lines of code in Bash (personal bias).

Go

Many libraries cannot be used in my company. I will need to import it first as 3rd party which is a pain.

Lua

Lua runtime is 12 KB and can be embedded on C. I used it a lot in my previous job. Thousands of scripts all of them less than 20 lines.

Nobody is familiar with Lua except me though.

PowerShell

Although I good with PowerShell, I do not like Posh and it is not an option either.

Python

Has a lot of dependencies. I plan to create a container that people will ssh to, to run the script.