From: "Zachary P. Landau" <kapheine@...>
Date: 2004-03-23T08:43:36+09:00
Subject: Re: Need some advice on PickAxe II

--NtwzykIc2mflq5ck
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 23, 2004 at 03:41:59AM +0900, Sam Roberts wrote:
> Wrote "Zachary P. Landau" <kapheine@hypa.net>, on Tue, Mar 23, 2004 at 03=
:21:04AM +0900:
> > > In its place, if you put a chapter on racc, on rexml, on webrick, on
> > > soap4r, etc., tutorial style stuff on how to do useful things, that's
> > > the kind of thing that I don't know will get done in the std lib
> > > documentation, and I would be happy to buy and be able to read on my
> > > couch, whereas it looks like the doc team (yeah team!) are doing good
> > > work in getting the per-API docs in better shape.
> > >=20
> >=20
> > I'm not sure I agree with this. Programming Ruby fits very well as an
> > introduction (and then reference) to the language itself. I think having
> > in-depth examples of how to use libraries is a job for another book
>=20
> But Programming Ruby V1 already has chapters such as I suggest!
>=20
> ch 14, ruby and the web (covers CGI and eruby, and integration in Apache)
> ch 15, ruby tk
> ch 16, ruby and windows (WIN32OLE, ...)

Oh yes, don't get me wrong, they would definitely be nice to have. But
if I had to choose one over the other, I'd choose having an entire list
of what is available as opposed to cutting out that section in order to
provide a couple chapters on how to use specific libraries.

I wouldn't mind paying an extra $10 or however much for a few more
chapters that go into detail. But if this isn't a choice, I choose a
for Programming Ruby 1.8 to lean towards a reference.

--
Zachary P. Landau <kapheine@hypa.net>
GPG: gpg --recv-key 0x24E5AD99 | http://kapheine.hypa.net/kapheine.asc

--NtwzykIc2mflq5ck
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAX3lbCwWyMCTlrZkRAvizAJ0agMLJ5W38ZBin6NsQyStw08X5TwCeOLPa
LDbTt88DV8N1Wb3/4PFq8E0=
=0Bl3
-----END PGP SIGNATURE-----

--NtwzykIc2mflq5ck--