It’s been a while. :) So, I ended up buying a Mac Mini, and last week I upgraded the RAM to 2 gigs so I’m sitting pretty well right now. (With the original 512 megs the Mini had at first, things were dog slow, especially when I tried to run Photoshop or InDesign. But now it’s quite fast. I am happy. :))

In other news, at work I’ve been coding a board game in Flash. It’s effectively my first Flash project ever (years and years ago I edited a company map in Flash, but it was so long ago that I can hardly remember it, and I was only maintaining it, so it doesn’t really count). Flash is smooth. I’m not completely satisfied with ActionScript, but it certainly works well enough, and I’m sure more experience with it will make it better. Overall, my time with Flash has been good and fun.

Finally, I’m hoping to get back into more Ruby/Python/Perl coding before too long. My new job’ll require some XML magic, for which I’ll probably use Python and XSLT. And in my typographical work on the side I’ll be doing a lot with TeX and either Ruby or Python.

All of which is to say, hopefully I’ll start blogging here more often. :)

After a month of OpenLaszlo, I’ve had enough. Coding in XML just isn’t my style, I’m afraid. (And yes, I know you do half the coding in JavaScript, but that doesn’t change anything.) I don’t think that means XML-based programming languages are inferior or anything like that — if I spent more time wrapping my head around OpenLaszlo, I could probably feel better about it (or I’d have one heck of a sore head). But I don’t have that kind of time. Nor was I getting enough of a “coolness” factor, the way I do when I work with Lisp. This experiment leads me to suspect that I probably wouldn’t like Flex much, either.

So, I’m going back to the basics. Simplicity is good, and so I’ve taken the app I’m working on and pared it down as far as possible. So far, in fact, that I’m pretty sure I’ll be able to do the whole thing with Javascript, HTML, and CSS, with a web service providing a connection to the server (written in ASP.NET most likely, though I’d prefer Python and may end up going that route), and anything else in Python. I might use MochiKit or Dojo to make the Javascript end easier to code, but I’m not sure yet if I really need it. (Why not Rails? Well, the server is unfortunately a Windows box running IIS, and I’ve heard that Rails doesn’t perform all that well on IIS. I wish I could get the server moved to Linux, but that’s probably not going to happen anytime soon. In the meantime, Python is still very nice to work with, and I haven’t caught wind of any performance issues with it on IIS.)

At any rate, this stack feels a lot better. When I was working with OpenLaszlo, I felt like I was in a straitjacket. Not much fun. Or “open.” (Again, keep in mind that these are subjective impressions; who knows, maybe OpenLaszlo is your style.)

In the meantime, I’m reading Paul Graham’s ANSI Common Lisp and liking it.

Technorati Tags: OpenLaszlo, Flex, Javascript, XML, Lisp, Python, MochiKit, Dojo, Paul Graham

I’ve been tinkering around a bit with OpenLaszlo, since here at work I’m about to start writing an RIA for doing online extraction of genealogical records, and it would be really nice not to have to re-invent the wheel. :) The advantages of OpenLaszlo are that it’s free, it compiles to Flash (which is on pretty much every computer out there) and soon DHTML, and it looks like it’s conducive to fast development. And there are a lot of high-profile apps using it (like Pandora).

So I spent half an hour throwing together a quick prototype of our app — no functionality, just the layout — and I think I’m liking it. It’s basically XML with a healthy dose of Javascript. Using XML this way feels almost like Lisp somehow, incidentally. :) So far I haven’t run into any huge roadblocks, so we’ll see if OpenLaszlo works for what I need.

Technorati Tags: OpenLaszlo, Flash, Pandora, XML, Javascript, Lisp

Finally started doing some Ruby coding today. I’m writing a pedigree parser that takes an XML pedigree and outputs it to HTML, and so the natural first step was to see what Ruby’s XML capabilities are. REXML is cool. I’ve done a fair amount of XML work in .NET at my job, and in spite of the differences, I was able to figure the basics out in a very short amount of time. That’s more a statement about how good Ruby and REXML are than it is one about my skill as a coder. :) Anyway, I seem to have heard about other XML libraries in Ruby (which makes me wonder if REXML has hidden deficiencies that I’m unaware of), but I won’t worry about those until I reach REXML’s limits.

And Ruby’s a delight to code in. I think I’ve grokked the block concept (myarray.each { |e| print e }, for example) and iterators and stuff like that. Now it’s just a matter of taking all those ingredients in my head and baking them into some real code. Then the mastery will start to come, and that’s when the real fun starts. I want to start coding DSLs (domain-specific languages) in Ruby, by the way… Mmm.

Can I just say that I love TextMate? Being able to run Ruby code straight from the editor (both via ⌘-R for the separate results window and through Control-Shift-E right in the editor window) is amazingly nice. Sure, other IDEs have that as well, but TextMate is delicious and fun to use.

Technorati Tags: Ruby, XML, REXML, TextMate