Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove TruffleRuby #4441

Merged
merged 1 commit into from Jan 14, 2017
Merged

Remove TruffleRuby #4441

merged 1 commit into from Jan 14, 2017

Conversation

chrisseaton
Copy link
Contributor

@chrisseaton chrisseaton commented Jan 14, 2017

Code still available at https://github.com/graalvm/truffleruby

@claudiug
Copy link

claudiug commented Jan 14, 2017

may I ask why remove TruffleRuby? That is a huge PR :)

@chrisseaton
Copy link
Contributor Author

@claudiug this mailing list post explains the reasons http://lists.ruby-lang.org/pipermail/jruby/2017-January/000511.html

TruffleRuby doesn't have any source code dependencies on JRuby anymore and hasn't for a while. We're having to tidy up our code base quite a bit in order to prepare for an ahead-of-time compiled (no JVM required) version of TruffleRuby that we are going release soon, and with both of those things it seemed time to start to develop in a separate repo.

@claudiug
Copy link

@chrisseaton thx for the quite fast reply.
AOT for ruby? wow

@chrisseaton
Copy link
Contributor Author

It's AOT for the Java program that implements an interpreter for Ruby, not AOT for the Ruby program. It's confusing I know.

It allows us to build a single, statically linked truffleruby executable that doesn't need a JVM to run, so much like the ruby executable you get with MRI. This reduces startup time by orders of magnitude, memory footprint, and deployment issues.

@chrisseaton chrisseaton merged commit 3e4fd9e into master Jan 14, 2017
@chrisseaton chrisseaton deleted the remove-truffle branch January 14, 2017 12:57
@enebo enebo added this to the truffle-dev milestone Mar 6, 2017
@enebo enebo added this to the Non-Release milestone Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants