administrative-scripting-with-julia VS DaemonMode.jl

I appreciate the "Why You Shouldn't Use Julia for Administrative Scripts" section[0] which asked exactly the questions I would have asked.

The choice of (non-Bash) language to write command line utilities is in a bit of odd spot right now. Python is basically almost everywhere installed but the dependency on runtime + venv oddities bring their own set of problems. Java has the same runtime need issues though things might improve with initiatives regarding native binary compilation (though including the runtime may not produce exactly lightweight executables). Perl used to be a hot favorite in this space but I don't think lot of people are writing new stuff in Perl even though it is still present by default almost everywhere. Go is almost perfect here except I don't want to deal with 3x the boilerplate. Personally I think Rust isn't a bad choice (libraries like clap hugely reduce the boilerplate) but the learning curve makes it a harder sell (even though for basic utilities, I don't think there would be too much wrestling with the borrow checker). Another choice that comes to mind is Nim; I think it is very well positioned except a lot of people don't know even about it so its a hard sell + even among those who know, everyone is looking at everyone else to take the initiative to adopt it in a corporate environment at a non-trivial scale.

[0]: https://github.com/ninjaaron/administrative-scripting-with-j...

My question is actually not what everyone uses, but what is best suited for the task. Those two things are, of course, almost always different, because the average person is anything but smart. Here you see that Julia is indeed better suited for handling data than Bash: https://github.com/ninjaaron/administrative-scripting-with-julia And here you see that Lisp will be the best scripting language for certain persons: https://quotepark.com/quotes/1879617-larry-wall-is-lisp-a-candidate-for-a-scripting-language-whil/ Obviously, if you don't have in-depth experience with both languages, you don't have to answer my question.

Thats for an entry point, you can search `Base.@main` to see a little summary of it. Later it will be able to be callable with `juliax` and `juliac` i.e. `~juliax test.jl` in shell.

DynamicalSystems looks like a heavy project. I don't think you can do much more on your own. There have been recent features in 1.10 that lets you just use the portion you need (just a weak dependency), and there is precompiletools.jl but these are on your side.

You can also look into https://github.com/dmolina/DaemonMode.jl for running a Julia process in the background and do your stuff in the shell without startup time until the standalone binaries are there.

> If I were to use e.g. Rust with polars, load time would be virtually none.

Because you're compiling...

And if you need to do the same in Julia, you should also pre-compile or some other method like https://github.com/dmolina/DaemonMode.jl (their demo shows loading a database, with subsequent loads after the first one taking roughly ~0.2% of the first)

Well, not nicely certainly, but:

https://github.com/dmolina/DaemonMode.jl

> portable

Neither is python - it just relies on universal availability. Over time…

You can get around a lot of these problems with DaemonMode.jl though.

You might want DaemonMode.jl

https://github.com/dmolina/DaemonMode.jl can possibly help in the future. Leaving it here so that people know this is planned.

If you strongly prefer to run scripts though, then you can use the package https://github.com/dmolina/DaemonMode.jl in order to re-use a Julia session between multiple scripts, saving you recompilation time.