Ruby vs Python
Apologies for the two posts in quick succession but I wanted to keep this post separate.
I've been planning to do a portal for my various websites for a while, drawing in rss feeds from my blog, my tumblelog, my Goodreads account and my new Magnolia account (which I am planning on replacing my delicious account because I prefer Magnolia and my delicious is in the biggest mess ever. I plan to do this in Rails and have done the initial steps in starting it.
Anyway, today, as I did some stuff on the site I wrote for work (which may soon be defunct) I was thinking how proud I was of it and how much of it I could use for other purposes. The category/topic system could be a category/blog post system. The devolved publishing/category system could allow for a multi-blog system where each user has their own separate blog. The REST knowledge that I've developed would help me write a client for it in the future. And the experience of writing a bilingual website means that I could write a proper bilingual site rather than just posting in alternate languages. Suddenly I had an aim for the future. Something to develop when/if I'm no longer developing at work.
And then I recalled how I've always wanted to learn Python, and had been complaining at last weekend's party that I need a project to enable me to do so. Could this be such a project? Of course, the first thing I'd need to do is find out if Dreamhost will run Python, and the first thing that comes up is this post: http://blog.dreamhosters.com/2006/05/24/django-on-dreamhost/. Rails-like framework for Python that will run on Dreamhost. So not only can I learn a new language but I can also use some of the concepts and techniques I've learnt through Rails. And Python is Lush. Not that Ruby isn't Lush. It's just not named Python.
I'm not definite about the framework yet. There may be better/alternate frameworks out there. But it looks like I've got long-term plans for a project. It will probably take me years, but I really want to do this! Although I still do plan to do the Rails portal in the near future.
I've been planning to do a portal for my various websites for a while, drawing in rss feeds from my blog, my tumblelog, my Goodreads account and my new Magnolia account (which I am planning on replacing my delicious account because I prefer Magnolia and my delicious is in the biggest mess ever. I plan to do this in Rails and have done the initial steps in starting it.
Anyway, today, as I did some stuff on the site I wrote for work (which may soon be defunct) I was thinking how proud I was of it and how much of it I could use for other purposes. The category/topic system could be a category/blog post system. The devolved publishing/category system could allow for a multi-blog system where each user has their own separate blog. The REST knowledge that I've developed would help me write a client for it in the future. And the experience of writing a bilingual website means that I could write a proper bilingual site rather than just posting in alternate languages. Suddenly I had an aim for the future. Something to develop when/if I'm no longer developing at work.
And then I recalled how I've always wanted to learn Python, and had been complaining at last weekend's party that I need a project to enable me to do so. Could this be such a project? Of course, the first thing I'd need to do is find out if Dreamhost will run Python, and the first thing that comes up is this post: http://blog.dreamhosters.com/2006/05/24/django-on-dreamhost/. Rails-like framework for Python that will run on Dreamhost. So not only can I learn a new language but I can also use some of the concepts and techniques I've learnt through Rails. And Python is Lush. Not that Ruby isn't Lush. It's just not named Python.
I'm not definite about the framework yet. There may be better/alternate frameworks out there. But it looks like I've got long-term plans for a project. It will probably take me years, but I really want to do this! Although I still do plan to do the Rails portal in the near future.