There are choices depending on your platform, such as therubyracer or therubyrhino to name a few. What gem and JS engine to use? Well, neither one of them. The reason behind this is fairly simple - you should stay as open as possible and try not to lock your users to a particular engine and the mostly native code behind it.
What’s the way out of this? There’s a great gem created by Sam Stephenson and other contributors called ExecJS. By depending on ExecJS you state that your gem needs a JS engine but you leave the rest onto the end users. ExecJS can automatically detect available JS engines and choose the most appropriate one. As of writing this text, there are 5 supported engines:
The end users decide what JS engine they want to or even can use on their target platforms. Often we have been burned by the therubyracer gem not being able to successfully compile on some BSD systems. By depending on ExecJS you allow users to easily solve this problem by for example installing a standalone Node.js.
Long story short, please think of your users and always use ExecJS instead of hard coded dependency.Written by Jiri Pospisil of sensible.io.
We're building a tool to help businesses reach out to their customers more easily. It's called SendingBee and it's going to be awesome.