dolhuis

I’m translating my java implementation of textile to Ruby now. It’s really a learning experience. Ofcourse it’s already done, but I have good reasons to do it again: partly to make it more extensible/flexible, partly because I want some things I didn’t get right away with redcloth.

I’m afraid I would do it al differently a second time around (but that shows you you learnt something).

There are some design patterns I have really difficulty with:

1) Static properties (with static accesors) and inheritance, seem to go counter to my intuition (subclasses seem unable to access them.)

2) Subclasses of built in classes don’t seem to behave as I expected (if I add a method in such a subclass, I get runtime errors that the built in class doesn’t have such a method.)

But Ruby is fun.

It is true: 37 of age and never driven a car, it just happened that way, no no-car fundamentalsm on my part.

I took my setup (Apache2 with virtual hosts, FastCGI, and Ruby on Rails) kicking and screaming into a working situation. So much stuff that didn’t work out of the box, it almost killed my interest in the whole project.

But I want to learn Ruby in conjunction with web-apps, because web-apps is my trade, and that’s where I’ll put Ruby probably to work. So it was kind of a prerequisit.

Next thing I want to do, is submit an article to Ruby on Rails, or something, detailing all the problems (and solutions) I encounterd.