From: Aaron Patterson <aaron@...>
Date: 2010-02-18T16:22:06+09:00
Subject: [ruby-core:28215] Removing Syck from ruby

Hello,

I have a ticket open to remove Syck from ruby:

  http://redmine.ruby-lang.org/issues/show/2340

I would like to move my replacement (Psych[1]) in to ruby's svn so that
people can start migrating to the new API.

Psych has a *mostly* compatible API with Syck.  Since Psych uses
libyaml, that means it follows the YAML spec more closely than Syck
does.  This means that switching from Syck to Psych /will/ break things.

I would like to remove Syck from ruby, and release it as a gem that I
will maintain.  That way people depending on the legacy behaviors of
Syck will not be let down, though they will be highly encouraged to
upgrade.

To ensure a smooth transition, I am working with the rails team[2], and
with Eric (for rubygems support).

Is this a good plan?

As a side note, it looks like people are submitting patches to libyaml
for Visual Studio support for windows[3], and that SnakeYAML provides an
evented API that mimics libyaml in pure Java[4].

I hope Nobu will help me with C89 support.  I remember the 1990s, just
not very clearly.  ;-)

[1] https://github.com/tenderlove/psych
[2] https://rails.lighthouseapp.com/projects/8994/tickets/3858-reducing-the-yaml-api-footprint#ticket-3858-1
[3] http://pyyaml.org/ticket/32
[4] http://code.google.com/p/snakeyaml/
-- 
Aaron Patterson
http://tenderlovemaking.com/