Huh, interesting. I bet for keyboard macros, it would work better by invoking a call to something that is already running to reduce startup time. Kinda like the emacs server.
BEAM should still be able to compile new code on the fly, for one-off scripts
> keyboard macros [...] would work better by invoking a call to something that is already running to reduce startup time
Maybe, but that comes with two disadvantages:
- I would have to re-architect my scripts to work like that, and run a server with uncertain memory costs perpetually; and
- I would have to use something with faster start time to run the call on my keyboard macros, e.g. bash, which would mean writing bash instead of elixir/ruby and/or being clever.
BEAM should still be able to compile new code on the fly, for one-off scripts