Like Haml, a work in progress…


We have readers checking this blog, asking what we are working on, how things are coming, or when we will do X? So I feel like we should post an update to briefly talk about what we are up to. We currently aren’t spending much time on company details (thankfully, much of it is now taken care of), and we are getting into coding. We have a pretty good idea of what features we will be trying to complete for the first release. We are currently trying to build the simplest version that will be useful. I think we have made good progress towards that goal.
Personally, I feel like my mind is starting to finally switch gears into the whole new project, language, and framework. I was expecting some downtime as my head flipped from the projects I was working on to this project, but it hasn’t been as bad as I was expecting. Today I think I was actually so deep and focused on the code that I wasn’t aware of anything going on around me. I think it is a good sign that I am starting to really get into the zone on our new project.
As far as the specifics of the code on our project, I don’t feel like there much I can reveal. We have been writing, refactoring, and reworking the code, along the way we have discovered some ups and downs of the ruby and rails. Hopefully, we will be able to share more about our discoveries when we get to a more stable and battle-tested code base.
I will mention briefly one specific issue we have run into with RoR: the templating engine Haml. We started working with Haml templates for some of our more complicated views. It was making the more complex views simpler, easier to read, and reducing LOC. Unfortunately we started to get some cryptic errors related to Haml, and we saw that Haml is still young and actively changing. On one occasion new Haml updates caused errors in our code. After spending some time tracking down the issues on a few occasions, we decided that Haml, while very cool, isn’t quite stable enough for our project. Since it is fairly easy to convert views back and forth between Haml and rhtml, we decided we would drop Haml for now. We are planning to take another look at it later after our changes slow down a bit, and see if the Haml project is a little more stable. For now, while nice, it just doesn’t provide a large enough benefit to deal with the extra debugging issues that have occurred. If you are working with RoR, I would recommend checking the project out, because it is definitely worth keeping your eye on.


One Response to “Like Haml, a work in progress…”

  1. Nathan Says:

    As a Haml developer, I’m curious to hear more details about what went wrong. It sounds like what you’re talking about are things that definitely shouldn’t have happened, and thus something that I’d like to fix.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: