opinions and rants on software and...things
April 17, 2008
I'm continuing to work on this blog software, and I am learning a lot about AppEngine, Python and Django. I used Django's include function to refactor the rendering of posts. That removed some code duplication. Got to love that. I feel like I've already done a full day's work, and it's only 10:30!
My inclination is next to look at extending Python's WSGIHandler further to make it more MVC-like. I'd never paid much attention to that design pattern before I started using Ruby on Rails, but I'm quite addicted to it now, and doing the extra work -- and admittedly, it's not that much -- to do it the AppEngine way irks me. I've already taken a step in that direction, subclassing RequestHandler to do all the work of creating a path to the appropriate template file and passing it to the render method, but I know that there's a lot more to do. I also feel like I could refactor the handling of the dictionary that passes values to the template to reduce the repititious setting of values that happens in each handler.
April 16, 2008
Learning to create Google App Engine applications via building this simple blog has been hugely fun and not just a little bit frustrating. Many, many thanks to Google's Marzia for so diligently helping me to figure out the missing piece that kept me from being able to upload this code.
I've come away from the experience feeling very enthusiastic about App Engine. It's not going to replace Ruby on Rails as my web development platform of choice, but I have to admit that GAE makes it very, very easy to quickly build and deploy an application. I managed to become a pretty competant Python programmer in just a few days, and I know enough about Django to build a small web application that observes the DRY principle.
I became very frustrated that Django is a whole seperate language unto itself, so I had to learn Python and Django. I suppose that I have become spolied by Rails, which allows me to write the logic, data and presentation layers in one language. It's so simple, beautiful and elegant.
That's not neccesarily an argument against GAE, which it seems is going to support multiple language and frameworks ...read more