Brilliant Corners

One of the first things I need to determine about THE PROJECT is what I'll build the application with. I'm positive I'll take advantage of one of the frameworks (like Ruby on Rails or CakePHP) to build the application, but I need to nail down which language I'll use. There are many many choices out there on what language to use, but for me there are only two I'll choose from: PHP or Ruby. But, which one? I've done quite a bit of work with both, although less with PHP. Let’s see the options:

Ruby

For the last three years, most of the work I've done has been with Ruby, either with Rails or, more recently, Merb. I grow more comfortable with Ruby every day and I still have fun learning new tricks. This had been pretty much restricted to Rails up until I gave Merb a try a few months ago. I rewrote this weblog with Merb and I had a good time teaching myself something new. Yes, there are many, many similarities between Rails and Merb, but I think there are some things that Merb does better (and easier). Rails, on the other hand, is a little more robust and has a larger community behind it. It could be easier to do what I want to (in the scope of this project) with Rails, as opposed to Merb.

PHP

In the last year, I've built a few web apps using the CakePHP framework, and I found it quite a nice change of pace to work with. Since I had a strong Rails background, CakePHP was easy to pick up since they certainly had Rails in mind when putting the framework together. However, if I went with PHP, I'm not sure I'd go with CakePHP. I've heard many good things about another framework, CodeIgniter, and I'm eager to try it. There’s nothing that particular bugged me about CakePHP, but CodeIgniter has a reputation as being a little faster, but it may not have a community as big as CakePHP’s backing it up, or as many places to look for code examples.

The Decision

So, what will it be? First of all, I think I can narrow it down to using Ruby instead of PHP. PHP is more widely supported (and easier to deploy, etc., etc.), but I think my day-to-day experience leans me more towards Ruby. I'm just more comfortable with Ruby than I am with PHP. I do want to use the CodeIgniter framework for something in the future (and I think I may already know what that is), but I just don’t think it’s quite right for this project.

That leaves me with the Ruby language, but which of the frameworks? Merb is just about to reach the big 1.0 milestone, but while Merb may be ready, I'm not sure I'm ready to build something big on the framework. It’s still young and with many fairly drastic changes in the API the last few months, there’s not a whole lot out there in the way of documentation and sample apps and code. In the few years I've been working with Ruby on Rails, the community has exploded with plugins for just about everything, tons of sample code, and a growing reference library (thanks to the Rails-related weblogs and numerous tutorials). I know Rails is up to the task, and that it can handle all that I'm wanting to do (and more).

In my mind, that settles it: I'll use Ruby on Rails.

At one point I had grand ambitions for the domain/site railstips.org. Sadly, I never acted on those ambitions. I kept it updated at first, only to eventually stop all activity. So, I figured that someone else could do something better with it.

I posted to the site asking if anyone wanted to take it over, and John Nunemaker took the bait. The transfer is complete, and already the site looks to be on the right track. And I just now noticed that John has posted his plans for the site. I'm now positive he’s the right person for the job.

Good luck with railstips.org, John!

I have yet again relaunched this weblog. This time I've done away with weblog applications that others have written and have rolled my own (yet again).

This time I've written a very simple weblog app with Ruby on Rails. It doesn’t do anything fancy, but that’s all right with me. I needed a simple project to get my Rails chops back in shape.

There are still a few things that may break or not work, but I think I've taken care of all the important stuff. If you do get an error or anything, please let me know.