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?


ongoing
software · G & M · Dad author · colophon · rights
picture of the day
Around August 17, 2006: RAD I: Why JRuby? · RAD II: Back to Ruby · RAD III: Quack Like a URI · Ceasefire · Back to the Mac

What?
· Technology (61 fragments)
· · Dynamic Languages (38 more)
· · Java (93 more)
· · Ruby (49 more)


Serif · Sans-Serif
I work at Sun Microsystems. The opinions expressed here are my own, and neither Sun nor any other party necessarily agrees with them.