\n
![](\"http:\/\/ec1.images-amazon.com\/images\/P\/0596100949.01._AA240_SCLZZZZZZZ_.jpg\")
\nThe author might as well have titled the book, “Java, Schmava – Ruby’s Where it’s At” and I expect this marks the last book he’ll write concerning Java. The rest will be about Ruby<\/a>. The book confirmed my feelings that Java has gotten way complicated over the years – far beyond the simple servlets I used to write.<\/p>\n
That said, I was impressed with the introduction of Ruby and what it can do. Recently I’ve found that my willingness to build web apps is tempered by my dread of building get another form to edit data in a database. It’s tedious and boring. I wrote a framework in PHP that discovers database schemas and creates objects for me, eliminating the need to write SQL most of the time, but that only goes so far. Ruby on Rails seems to have solved the database abstraction problem and the web interface problem.<\/p>\n
Personally, I’d like to be able to settle on one programming language. Since every browser in the world supports JavaScript, it’s clear that language isn’t going anywhere, so it might as well be JavaScript. Unfortunately it hasn’t caught on in servers, despite support in IIS. It just drives me crazy keeping syntax straight while flipping back and forth between editors in Perl, PHP and JavaScript. <\/p>\n
I’ve got a little tool I’ve been putting off writing and this book helped convince me that I should write it in Ruby. We’ll see how it goes.<\/p>\n","protected":false},"excerpt":{"rendered":"
The other day someone asked me if I had written anything Python. My response was a quick “no”. I’ve invested a lot of time in Perl and PHP (and to some extent Java) and I’d have to have a really good reason to learn Yet Another Programming Language. CPAN and Pear are rich API libraries …<\/p>\n