Now this is where Ruby is winning, so many different implementations, and that too successful ones! I love the community. Congratulations to the team. :-)
Rubinius 1.0 (Fabius) Released
11–20 of 50 posts
Re: Rubinius 1.0 (Fabius) Released
#12Congrats to Evan and the team! Now that 1.0 is out, how about adding a blog and a mailing list? I'd love to see Rubinius pick up a large following. IRC-only makes it a challenge to build a thriving community.
We have a mailing list at http://groups.google.com/group/rubinius-dev, though it hasn't taken off much yet. Perhaps now that 1.0 is out people will use it more.
Blog wise, what would you like to see on a Rubinius blog?
Re: Rubinius 1.0 (Fabius) Released
#13Earlier quoted context omitted.
The biggest goal, at least a few years ago, was to have a Ruby that is substantially implemented in Ruby, as opposed to being a hundred thousand lines of C under the hood. Paradoxically, this can result in speedups, since it's easier to optimize expressive, well-written code. Avi Bryant gave a talk at RailsConf a few years ago about how Smalltalk contains all the "features" of Ruby that are usually blamed for its per…
I think they are on the right track. Given that this is a 3 year old project, I don't think we can compare it to smalltalk implementation with years of development. I wonder how well it would compare to something like pypy and other similar projects.
Better question: What happens if companies like google start eyeballing it and putting some real money behind it.
Re: Rubinius 1.0 (Fabius) Released
#14Congrats to Evan and the team! Now that 1.0 is out, how about adding a blog and a mailing list? I'd love to see Rubinius pick up a large following. IRC-only makes it a challenge to build a thriving community.
We have a mailing list at http://groups.google.com/group/rubinius-dev , though it hasn't taken off much yet. Perhaps now that 1.0 is out people will use it more. Blog wise, what would you like to see on a Rubinius blog?
Off the top of my head: internals, neat optimization tricks, updates on development, how to hack.
Re: Rubinius 1.0 (Fabius) Released
#15I'd like to see if / how many of my unit tests pass using Rubinius, but does it currently support 1.9-specific code?
Also, RVM installs RC2, not the 1.0 release. Maybe someone can give them a poke...
UPDATE: Nevermind, http://rubini.us clearly states that 1.9 compatibility will happen post-1.0. Can't wait, even if it's just to know that my code is compatible with what may be a very real option in the years to come.
AND: I should probably run "rvm update" first, to get the 1.0 release...
Re: Rubinius 1.0 (Fabius) Released
#16One thing I'd appreciate with these kinds of announcements is a "what is it" paragraph preferably towards the top of the referenced web page. I suppose if I were working in Ruby I'd know what Rubinius is and why I'd care but a list of "what is new" doesn't particularly help me or folk like me.
If you worked in Ruby you'd definitely know that Rubinius is one of the next-gen Ruby VMs. Since you don't work in Ruby, the whole project matters a lot less to you.
Re: Rubinius 1.0 (Fabius) Released
#17I'd like to see if / how many of my unit tests pass using Rubinius, but does it currently support 1.9-specific code? Also, RVM installs RC2, not the 1.0 release. Maybe someone can give them a poke... UPDATE: Nevermind, http://rubini.us clearly states that 1.9 compatibility will happen post-1.0. Can't wait, even if it's just to know that my code is compatible with what may be a very real option in the years to come. A…
Just updated rvm and can confirm 1.0.0 it's there.
Re: Rubinius 1.0 (Fabius) Released
#18Congrats to Evan and the team! Now that 1.0 is out, how about adding a blog and a mailing list? I'd love to see Rubinius pick up a large following. IRC-only makes it a challenge to build a thriving community.
We have a mailing list at http://groups.google.com/group/rubinius-dev , though it hasn't taken off much yet. Perhaps now that 1.0 is out people will use it more. Blog wise, what would you like to see on a Rubinius blog?
Would love to see a big fat link on the front page that says "Help make the best Ruby implementation ever. Join us!" with a link to the google group. Clear call to action.
Blog wise: Bubble up some of the great activity going on behind the scenes. Design decisions, great implementation debates, calls for help on hard/easy problems, new releases, beta releases, testing calls, etc. The posts don't have to be more than a paragraph or two. Just enough so we can see where you guys are steering the ship and if there's something we can do to help.
I'm sure there are more than a handful of potential up and coming language implementers that Rubinius could help inspire and recruit. All it takes is an easy to find/read active conversation to get them engaged.
Also, I'm sure you're thinking about a 'the long road to 1.0' post. That would be great first post to talk about all the decisions and direction changes that lead up to the current design.
Re: Rubinius 1.0 (Fabius) Released
#19One thing I'd appreciate with these kinds of announcements is a "what is it" paragraph preferably towards the top of the referenced web page. I suppose if I were working in Ruby I'd know what Rubinius is and why I'd care but a list of "what is new" doesn't particularly help me or folk like me.
Was going to say the same thing. Just looked through the site trying to find exactly what it is, and all I got is:
1. It's a Ruby implementation.
2. It's mostly compatible w/ Ruby & its components (Rails, gems, etc.) but not completely.
3. ... ?
An About page would be nice - answer these questions, among others:
1. What is Rubinious?
2. What differentiates it from Ruby?
3. What problems does it solve?
4. Why would Ruby programmers want to use it?
5. Why would non-Ruby programmers want to use it?
Re: Rubinius 1.0 (Fabius) Released
#20This is my favorite project we have at Engine Yard. I've been rooting for it and fighting to keep it alive for years now because I know that this is the future of ruby. Evan and Brian and all the contributors have done great work on this ambitious project.
I've had ruby aliased to rbx on my own personal laptop and run all of my development on rbx, I only have to bust out MRI every once in a while, like once a month. I write lots of code with event machine, redis, amqp and many other complex parts of ruby ecosystem and for the most part they all just work on rbx.
Huge congrats to rubinius team again, I predict this will be the default ruby for most people inside of a year if not 6 months.
Rubinius is ruby done right IMHO.