# Ruby as an expression language

**URL:** <https://forum.openrefine.org/t/ruby-as-an-expression-language/1549>\
**Category:** Development & Design\
**Created:** [May 26, 2024, 7:54am UTC](https://forum.openrefine.org/t/ruby-as-an-expression-language/1549 "2024-05-26T07:54:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thadguidry](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/thadguidry/32/653_2.png) [@thadguidry](https://forum.openrefine.org/u/thadguidry)\
**Post date:** [May 26, 2024, 7:54am UTC](https://forum.openrefine.org/t/ruby-as-an-expression-language/1549/1 "2024-05-26T07:54:21Z")

</div>

Looks like with JRuby and in particular now that it has JRuby Embed (old name Red Bridge), it should be easy enough to do a similar setup I did for Groovy and passing shared data of OpenRefine objects and fields to JRuby, according to their docs.

I'll work on that next week! Stay tuned for the next scripting language support!

---

<div class="post-metadata">

**Author:** ![thadguidry](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/thadguidry/32/653_2.png) [@thadguidry](https://forum.openrefine.org/u/thadguidry)\
**Post date:** [May 26, 2024, 8:00am UTC](https://forum.openrefine.org/t/ruby-as-an-expression-language/1549/2 "2024-05-26T08:00:53Z")

</div>

The idea for adding more scripting languages, is so that we can try to cultivate even more users of OpenRefine that might be scientists or data architects that might know a particular scripting language already. All the while we can continue to try to make GREL even better and easier to use in the future (like new functions, better error reporting, linting, etc.)