DaemonMode.jl VS StaticTools.jl

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.

It's not beta. I mean PackageCompiler.jl (used in production, by e.g. PumasAI company, a huge success) which makes though non-small binaries. Other tools for tiny binaries (and limited subset of Julia), are yes "experimental" but work: https://github.com/brenhinkeller/StaticTools.jl

We already have some forward prototypes of being able to run Julia ahead-of-time compiled native code from the command line.

https://github.com/brenhinkeller/StaticTools.jl

I think what we'll end up with is a language that can be used in both a fully static mode and in a dynamic mode along with some possible mixing. We may yet get the benefits of a statically compiled language as the tooling continues to develop. I do not see anything inherent in the language that would prevent that from happening.

https://github.com/brenhinkeller/StaticTools.jl is meant to facilitate this.