When
· Naughties
· · 2006
· · · August
· · · · 17 (2 entries)
The Ruby Ape Diaries · I took tons of notes while I was working on the Ape. I was going to hold off publishing till I released the code, but once I actually launched the formal Sun process to do that, I discovered that it can take two or three weeks, and so I decided to go ahead while it was fresh in my mind. Unfortunately, the piece pretty soon had fifteen different sections and would have been too long for mere mortals with jobs to read, and furthermore, the sections didn’t have much to do with each other, and there just aren’t that many people on earth who’d be interested in all of them. Some of them look close at the issues of making Java and Ruby get along, while others wallow in duck-typing perversity and finer points of Ruby style. So I’ll keep them short and do one a day (or so) for the next week (or so) and fill a table of contents in here.
I. Why JRuby?
II. Back to Ruby
III. Quack Like a URI
IV. TMTOWTDI
V. << !!
VI. Java APIs from JRuby
VII. J?REXML
VIII. Surface Phenomena
IX. Those Libraries
X. Making Markup
XI. Where To?
I. Why JRuby?
II. Back to Ruby
III. Quack Like a URI
IV. TMTOWTDI
V. << !!
VI. Java APIs from JRuby
VII. J?REXML
VIII. Surface Phenomena
IX. Those Libraries
X. Making Markup
XI. Where To?
RAD I: Why JRuby? · [RAD stands for Ruby Ape Diaries, of which this is part I.] To build a validator you need an HTTP engine and an XML parser, both of which Ruby is advertised as having. JRuby, when I first took this on, was as at release 0.9.0 and had plenty of rough edges. But I decided to use it anyhow ...
