# Should Elixir replace Ruby for simple scripting?

**URL:** <https://forum.elixirforum.com/t/should-elixir-replace-ruby-for-simple-scripting/58214>\
**Category:** Discussions\
**Tags:** ruby, script\
**Created:** [September 11, 2023, 4:19am UTC](https://forum.elixirforum.com/t/should-elixir-replace-ruby-for-simple-scripting/58214 "2023-09-11T04:19:16Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![D4no0](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/d4no0/32/33624_2.png) [@D4no0](https://forum.elixirforum.com/u/D4no0)\
**Post date:** [September 11, 2023, 12:12pm UTC](https://forum.elixirforum.com/t/should-elixir-replace-ruby-for-simple-scripting/58214/6 "2023-09-11T12:12:21Z")

</div>

> [@dimitarvp](#):
>
> Many of us would wet their pants if the BEAM has CLI parameters that would allow it to boot much faster (maybe at the cost of initializing apps slower? no idea), trust me. There was a discussion some months ago about it and there were various options listed even by core Erlang maintainers but none of them truly helped.

I think it would be nice, however I think this is not the right tool for CLI applications, at least not in the fashion of run this command and close.

I’ve had this problem before on a project, and what I ended up doing is to switch the strategy to a long-running process, that basically receives input and generates the output without closing the process, but of course there are many potential problems with this approach.

---

_[View the full topic](https://forum.elixirforum.com/t/should-elixir-replace-ruby-for-simple-scripting/58214)._