Well, Steve Jobs threw us all a litle curveball there. Everyone was expecting Intel iBooks, not Intel “PowerBooks”. But alas, the PowerBook is what we got! Although it’s been renamed to the MacBook Pro. I assume the iBooks will be called MacBooks also once they’re Intelized. Anyway, I can’t afford to get one just yet. But several months from now, I will be replacing my PowerBook with a MacBook, and I’m stoked!
Adventures in Ruby
My little attempt to sneak Ruby on Rails into my workplace is going well. I’m definitely committed to it at this point for this project. We’ve ended up with a lot more integration-type work than I was originally expecting. While I can’t give too many details, the project essentially entails accepting data embedded systems, and table PCs, and running various calculations on them.
At this point, I’m using Rails and Mozilla (set to kiosk mode) for the tablet PCs. The Tablet PC pings Rails via AJAX every couple of seconds for new information. The Rails server uses Distributed Ruby (DRb) to connect to a master application (plain ol’ Ruby service). The plain-ol-Ruby application is ALSO accepting web service calls from Java application on the embedded systems. (The Java application is, itself, just translating calls from a C++ application).
OH, and I didn’t get to start coding anything until late last week, and it’s supposed to be complete next week sometime. So it’s very exciting times indeed. Nevertheless, this is a good experiment, using Ruby in a production environment with a near-impossible deadline that MUST be met.
Personal Projects
The thing I love about Ruby the most it the practically none-existent barrier-to-entry when it comes to quickly prototyping your ideas. In Java, I wouldn’t even start a project unless I was sure it was something I wanted to do. Now I just start. A good example of that: how many database schemas did you have on your machine before Rails? And after? MySQL had a good 4 or 5 databases on my laptop – pre Rails. Now I’ve got over 25 and growing rapidly. "rails <great\_new\_application>" is just too easy to do. In an hour you can have a decent skeleton of your idea, see it working, and THEN decide if it sucks or not.
Anyway, back to work I go.