I am proud to announce the launch of Classowl.com. We are currently in Private Alpha, so we won’t be able to give any information about it for a few more weeks. This has been a project of mine for over a year now, and I am really excited to see all the hard work that Okapi and I have put into this product come to fruition.

Sign up to be notified when we release Beta!

We are currently developing two applications at Okapi; one with Ruby on Rails, and one with Django. While Ruby on Rails the most popular Web Frameworks these days, there is a ever growing Django following, which was open sourced about a year after Ruby on Rails was.

I found Django thanks to Kristopher Tate, CTO & Founder of Zooomr.com. I was looking for a framework that was FAST, and I had been on Zooomr.com quite a bit and really liked how fast the pages rendered. I was also looking for something that was built on Python, because a large part of Google and Facebook use Python. They too are some of the fastest sites on earth. So I pinged Kris one day on Skype and we had a nice chat about web frameworks. In the end, I was sold on Django; I had never heard about it before, but if this 18 year old hacker genius recommends it, I better get on board.

The main differences between Ruby on Rails and Django is simply the languages behind them. Rails is (obviously) built on Ruby, whereas Django is built on Python. Rails was born out of BasecampHQ.com, Django was born out of Lawrence.com. When put to speed tests, Django clearly beats Rails.

I think one of the main reasons Ruby on Rails took off and Django really hasn’t is because of how much better Rails has been marketed. 37signals, the company responsible for creating Rails, is a design studio that is famous for simple, elegant, usable design. Django never really had a innovative design studio/person loudly backing it. Zooomr is very innovative, but I have never once read an article talking about Zooomr’s use of Django.

As I said earlier, Okapi is currently building two applications. The one using Ruby on Rails is a simple time tracker for freelancers and small design studios. People will be able to use this to track all of their invoices, instead of wasting time with an Excel spreadsheet every time they are done for the day on a certain client. More on this application soon. The one using Django is a Client Management System for Moreno & Associates; a client of ours that we are currently rebranding. We have been talking about modifying the application and commercializing it, we will let people know if we do.

Overall, the two frameworks have been nothing but amazing for everyone on the team that is using them in development. We look forward to using Ruby on Rails and Django in the future for clients.

At OkapiStudio we always stay in touch with the latest trends out there related to web, print, motion and many other aspects of our daily business activity. Not long after the Web 2.0 boom, people are already starting to talk about Web 3.0 and its semantic aspect, about software acting like a service and other things related to this unprecedented fast and efficient evolution of the technology.

The Rails framework for Ruby, created by David Heinemeier Hansson, a partner with 37Signals (I am sure Sam will dedicate a few posts to H. H. himself), aims to increase the speed and ease of web development. You will find Rails associated with many true Web 2.0 applications.

We did research on both Ruby and Rails for a few days. Working on a Mac OS X environment, we found the installation to be a true quest and fastidious process. While on PC you have a fast installer, on Mac there is an entire process that involves spending a few hours in front of a black command prompter terminal. And if you start installing it don’t do it at 3 AM, please be fresh, do it in the morning, without too many things on your mind. I messed up the installation process 3 times on my machine before getting it right. There is a great aspect to this though, Apple will start shipping Rails with it’s next version of OS X, Leopard.

After browsing two Rails books we started the tutorials. I personally didn’t write any line of code and felt that after the experience with the installation process an even harder process will begin. I was thinking that perhaps we’re just wasting time and we should focus our energy on other aspects of our business. And i couldn’t have been any wronger.

Not even one hour later, Gabi, with a big and amazed smile on his face was having a first fully functional Rails application working. Nothing fancy, just some basic input of information into a database, with editing and sorting and a couple of other features. It was “magic”, this is the word the Rails guys are using, mostly because you use few lines of code and commands to trigger so many processes in the background that generate fast results.

And i will explain this magic by an example so you would understand even though you never wrote a single line of code in your life.

A few days later, working on a timesheet application we initially planned to have developed in PHP, our fellow programmer Corneliu was stating “it would have taken me 3 days to do the code for the same functionality you did in Rails in just 3 hours”. We’ll post the first screenshots of an incipient Alpha release in a few days.

We appreciate Rails because it truly stands up to it’s promise to ease and speed up the web development process.