hoodwink.d enhanced
RSS
2.0
XHTML
1.0

RedHanded

RubySpaMeeting2006 #

by daigo in cult

We have, right now, an over-night offsite meeting at a spa in Matsue, where Matz lives. 20 Rubyists comes here, including Matz and a few NaCl’s staff, Nakada-san, Sasada-san, Takahashi-san and many.

Takahashi-san discussed the details of Japan Ruby Conference 2006, which will be hold at June, a renewal plan of Ruby Reference manual and so forth. The new one with a steady, common format which is refe and ri friendly will come out at July.

Matz has decided a release plan for some Ruby 2.0 features.

  1. YARV will be merged into Ruby 1.9 at Feb 14, Saint Valentine’s Day.
  2. He has fixed the SelectorNamespace specification, however, which is only in his mind now.
  3. The multi language support, which he has implemented almost completely, will be shortly committed with a CVS tag. Be careful that it breaks the compatibility of Marshal.
  4. Generational GC will NOT be included in Ruby 2.0 unless somebody tries to build.
said on 04 Feb 2006 at 11:23

oooo Yarv.

said on 04 Feb 2006 at 11:41

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

said on 04 Feb 2006 at 11:46

AWESOME! Way to go guys!

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

said on 04 Feb 2006 at 12:28

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

said on 04 Feb 2006 at 13:02

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

said on 04 Feb 2006 at 13:26

- now

said on 04 Feb 2006 at 13:35

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?

said on 04 Feb 2006 at 15:23

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.

said on 04 Feb 2006 at 16:38

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

said on 04 Feb 2006 at 18:43

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.

said on 04 Feb 2006 at 21:26

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?

said on 04 Feb 2006 at 21:27

forgot to say: thanks for the report daigo!

said on 05 Feb 2006 at 04:40

What’s YARV ?

said on 05 Feb 2006 at 04:44

Great news ;-)

said on 05 Feb 2006 at 07:36

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?

said on 05 Feb 2006 at 14:32

Matz lives in a spa? Sweet!

said on 05 Feb 2006 at 16:47

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.

said on 05 Feb 2006 at 22:41

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

said on 06 Feb 2006 at 00:36

What’s Ruby’s official alcoholic beverage?

said on 06 Feb 2006 at 02:32

Sake?

said on 06 Feb 2006 at 08:53
said on 06 Feb 2006 at 15:59

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.

said on 06 Feb 2006 at 16:33

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

said on 07 Feb 2006 at 07:35

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.

said on 07 Feb 2006 at 09:31

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.

said on 07 Feb 2006 at 11:41

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).

said on 07 Feb 2006 at 14:29

Corvid, make sure to

./configure—enable-pthread

when compiling the rite version of yarv

said on 08 Feb 2006 at 12:19

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

I think the answer is clear.

said on 08 Feb 2006 at 13:03

is this what you drink after converting something from Java ?

said on 10 Feb 2006 at 04:11

i think i’ve heard that ocaml has a pretty nifty GC. Any expert info on that here?

said on 19 Feb 2006 at 04:28
toby: I’m not a GC guru, just quoting mr. Bohem:

“The collector uses a mark-sweep algorithm. It provides incremental and generational collection under operating systems which provide the right kind of virtual memory support.”

Comments are closed for this entry.