|
| 1 | +--- |
| 2 | +layout: doc_en |
| 3 | +title: Frequently Asked Questions |
| 4 | +previous: Index of Terms |
| 5 | +previous_url: index-of-terms |
| 6 | +--- |
| 7 | + |
| 8 | +## Can I hide source code using Rubinius' byte code format? |
| 9 | + |
| 10 | +No. Rubinius' byte code format provides no mechanisms to obfuscate the |
| 11 | +contents of it or the original source code. Source code obfuscation will never |
| 12 | +be added to the byte code format. |
| 13 | + |
| 14 | +## Does Rubinius support ARM? |
| 15 | + |
| 16 | +Not entirely. Currently the JIT does not support ARM and as such you'll have to |
| 17 | +disable it if you want to run Rubinius on ARM. Even then we can't guarantee |
| 18 | +that Rubinius will work reliably on this architecture. We hope to support ARM |
| 19 | +in the future. |
| 20 | + |
| 21 | +For more information, see the following issues: |
| 22 | + |
| 23 | +* <https://github.com/rubinius/rubinius/issues/2867> |
| 24 | +* <https://github.com/rubinius/rubinius/issues/2331> |
| 25 | + |
| 26 | +## Does Rubinius support Windows? |
| 27 | + |
| 28 | +No, not at the moment. While we would love to support Windows we sadly don't |
| 29 | +have anybody with Windows experience on the team. A corresponding issue for |
| 30 | +this can be found at <https://github.com/rubinius/rubinius/issues/2882>. |
| 31 | + |
| 32 | +If you would like to help with getting Rubinius running on Windows please get |
| 33 | +in touch. |
| 34 | + |
| 35 | +## Why is the README of Rubinius in plain text? |
| 36 | + |
| 37 | +Various developers have opened pull requests over time to change the plain text |
| 38 | +README to a Markdown formatted README. Due to the simplicity of the README we |
| 39 | +have decided to keep it plain text only. |
| 40 | + |
| 41 | +For more information, see the following: |
| 42 | + |
| 43 | +* <https://github.com/rubinius/rubinius/pull/1007> |
| 44 | +* <https://github.com/rubinius/rubinius/pull/2903> |
| 45 | +* <https://github.com/rubinius/rubinius/pull/1603> |
| 46 | + |
| 47 | +## What are all these rubysl Gems doing in my Rubinius installation? |
| 48 | + |
| 49 | +Rubinius uses Gems for its standard library. For example, `rubysl-date` is a |
| 50 | +Gem containing the `Date` library used by Rubinius. These components are |
| 51 | +installed, updated and otherwise maintained as ordinary Gems. |
| 52 | + |
| 53 | +Although you can technically remove then it is not recommended to do so. Due to |
| 54 | +these components being used throughout the Rubinius & Ruby ecosystem you might |
| 55 | +end up with a broken installation if you remove them. |
0 commit comments