From: "Sean E. Russell" <ser@...>
Date: 2004-02-12T06:24:24+09:00
Subject: Re: Standard libraries


--Boundary-02=_r1pKAJI7u1uxdAh
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 11 February 2004 15:54, Dave Thomas wrote:
> > What happens when some new functionality gets added?  IE, what do you
> > deprecate when LDAP support is added to the library set?
>
> one of the three option parsing libraries, perhaps, or delegate.rb. My
> point is that it's very easy to add new things, but there's an art to
> deleting stuff as well. We're building up a list of things in the
> standard distribute which are effectively obsolete, and we need to
> start thinking about rationalizing the situation.

I see your point.  IMO, it is better to have no rule, than one that is=20
ignored, and this one has a high probability of being ignored.

I would tend to agree with you that hindering bloat is a good thing,=20
especially in something like Ruby.  I'm just considering that Ruby now=20
contains two projects that pretty clearly overlap in problem domain: REXML=
=20
and YAML.  I'm wondering what existing library would have been removed had =
we=20
had rule #2, and which of the two new projects would have been chosen for=20
exclusion.  I think the people who want XML support want it because XML is =
a=20
standard, and people who want YAML want it because XML is too heavy for a l=
ot=20
of projects, and because YAML is more in tune with the simplicity of functi=
on=20
that Ruby typifies.

=2D-=20
### SER  =20
### Deutsch|Esperanto|Francaise|Linux|XML|Java|Ruby|Aikido
### http://www.germane-software.com/~ser  jabber.com:ser  ICQ:83578737=20
### GPG: http://www.germane-software.com/~ser/Security/ser_public.gpg

--Boundary-02=_r1pKAJI7u1uxdAh
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAKp1rP0KxygnleI8RAhggAJ4gYvuwbVfXzFOMBG8wpiw0Xs9qEwCfQKEq
vICPNqW4noxCyQzsmTU0HUA=
=EYtZ
-----END PGP SIGNATURE-----

--Boundary-02=_r1pKAJI7u1uxdAh--