Thanks a lot of this gem!!! And a suggestion.

[jikkujose]

Its been over an year I was toying with this idea. Have been thinking ways to make it elegant. I really feel this surpasses what I had dreamed off. Frankly, I had never used ActiveSupport, just knew it as a part of Rails. Seeing it can be used like this is also great.

So, I was testing this extensively and I noticed something - its quite slow; I know its not a surprise. But while discussing with a few friends many pointed that its not exactly because of the time to execute the commands but its the time to initiate the process. If then, I was wondering if we could somehow have a REPL kind of environment running in the background and have the output passed into the terminal almost instantly? I would assume the overhead to be minimal and for people who uses this often, it may well be justified. Thoughts?

[tombenner]

That's certainly a possibility, but it'd be better if we could speed up the executable itself. Almost all of the initialization time is spent loading Active Support, unfortunately. I'm looking into options, but if anyone has any ideas, definitely feel free to post them here.

[pdai1y]

I apologize as I am fairly new to ruby, but could something like sidekiq be if use to achieve what @jikkujose described?

Awesome work! :D

[jikkujose]

Do you mean to say that substantial performance gains can be achieved by disabling ActiveSupport? If then a global setting or even a flag might be a quick fix?

[jikkujose]

Haven't used SideKiq yet; but it seems it will be great for the job!