oooo Yarv.

And selector namespaces and multi-language support, oh my!

AWESOME! Way to go guys!

Now we can finally stop asking you “What’s going on with YARV ?” =)

rats, I can’t get yarv-3.3.0 to compile (fails at the link stage with thread.o). :(

multi language support → Is this unicode support, or does Ruby now run Perl and Python code now ><

- now

Wow yarv in 1.9 on valentines day! Thats sweet. Is it compatible with all the 1.9 syntax or are there some things missing still?

Great news! :-)

I love so much Ruby and Matz and all the developers and users of Ruby that, that, that…

Awesome gems you all are.

typo in article: Mershal should be Marshal. FOR -SHAME.

All the Greats, sittin in bubbles and salts, havin a schvitz. This is just what 1.9 needs. You guys have a good night at the RelaxFest, Daigo.

corvid, try the svn version, I have it working with gcc on ubuntu and win32. And now it runs a large parte of “make test-all” : ~400 tests plus yarv’s own ones.

Nice, ain’t it?

forgot to say: thanks for the report daigo!

What’s YARV ?

Great news ;-)

How about something even better than generational GC, e.g. incremental tri-color write barrier GC (a la Io)? Any plans for a non-pausing GC? Or just the same old mark-sweep action?

Matz lives in a spa? Sweet!

toby: I think that incrementality is ortoghonal to “generationality”, the former is relative to how you cleanup the stuff (a lil bit at a time or pausing or concurrently) the latter to how you find stuff. It seem to me that saying that Io’s GC is tri-color basically means that it works with three generations.

Anyway, I wonder if we could provide a—enable-bohem-gc switch, since it is now bundled with a lot of other projects (gcj, gnu ObjC, mono, various lisps/schemes, even W3M :), and IIRC it is an incremental generational compacting collector with impressive performance.

The very important fact: I have gotten drunk very much ;-)

What’s Ruby’s official alcoholic beverage?

Sake?

yes, but not just any sake.

It would be a good idea to get some word from Matz about what type of sake we should drink when a Ruby based product ships/hits 1.0/we feel like getting “crunk”, as it were.

I love sake. Matz and some rubyists don’t drink.

riffraff: Boehm GC is mark-sweep, just like Ruby’s. See this page for more info on libboehm. In addition, the term tri-color does not indicate generationality of the garbage discovery, but rather it is a marking technique that is fundamental to incremental GC. Check out this synopsis for more info on that and other GC techniques (great site, right there).

I only ask about incremental GC because its taken Java so long to get generational GC to the point where I don’t want to stab Gosling with a #2 Dixon-Ticonderoga every time I fire up a JVM and I don’t want that to happen to Ruby. In addition, Perl and Python use simple reference counters and Io does the incremental thing, as I’ve said. (I wonder what Lua uses?) I would lean towards simple and effective versus generational GC for YARV /Ruby 2.0.

There are less drinkers and smokers in Japanese Rubyists than Japanese average. At that dinner a half of people including Matz and me did not drink at all (we had a little drink fee in the bill). And we had one or two smokers.

I hear that industries with the high ratio of smokers is likely to wear suits.

Having had a lot of experience with it in Inkscape, I don’t see that the Boehm collector would necessarily present an advantage over Ruby’s current one; it would need to be even more conservative than Ruby’s current mostly-precise setup (IIRC, Ruby is only conservative about scanning the stack/registers).

Corvid, make sure to

./configure—enable-pthread

when compiling the rite version of yarv

“What’s Ruby’s official alcoholic beverage?”

I think the answer is clear.