« "Web 2.0" is so Web 1.0(ish) | Main | Safari now supports LiveGrid & AjaxEngine »

October 27, 2005


David Heinemeier Hansson

Congrats on the launch. What did you port from?

Richard Cowin


The original version was in J2EE.

Even though the java code was a bit more verbose than it could have been, the new ruby code was a full order of maginitude smaller. The new code base is much more cleaner and habitable than the original.

I did some quick benchmarks before I shut the J2EE server down. The rails version was running about 2-10% faster.


Congrats. I've been wanting to take a look at Ruby on Rails. I wish that there existed already a CMS and ecommerce open source solution that ran on it...I need it last week. This may be offtopic, but for existing sites with content, what would you suggest that data be saved in xml or a database?

Chris Clarke

I am looking forward to the new stuff. I am using in my spyce(python) app right now. Spyce is a bit php like but thanks to rico I am able to get a cleaner separation between presentation and app. logic its not quite MVC but..
It took me a while to figure it out but it was well worth the trouble
One problem i am having is with IE 6 (6.0.2800.1106) even the livegrid.page does not work (although it did a few weeks ago???)
On some of my own stuff IE starts displaying the page and then complains that it can't find the url
Firefox of course works perfectly
I notice that the yahoo search works but there is no documentation on it
Is there some patch that i can apply or something??
I am using 1.1 beta2 (prototype 1.3.1)


Richard Cowin

I expect your decision might be impacted by how the content is currently stored.
I prefer to store content in databases and use XML for a transport format.
Ruby on Rails makes databases easy to use for storing your content. It also has a nice xml template option RXML that can be used instead of RHTML. I have also created a wrapper around received xml content that makes it easy to navigate through. I will post on it in the next day or two.

Richard Cowin

Thanks for pointing out the issue with the demo on IE. It turned out to be an issue with a comma in the options on the html page. Should be all resolved now.

Now that I have all the demos in Rails, I will do some write ups on how they are implemented and will also include all the source. The Yahoo demo will be the first I cover. I will also cover a XML wrapper that was used in the Yahoo and Weather demo that supported much cleaner code.

We will be releasing a release candidate for 1.1 soon.


Richard, Are you planning on updatig Rico to play nice with prototype 1.4.0_rc1? Unfortunately I use some of the scriptaculous goodies, but I strongly prefer your drag-drop and they don't play well together.

Maybe I'll take a look at all the latest from everybody and see what's involved in makiing the changes to Rico.


Richard- you can ignore my comment above... I just updated a bunch of stuff and it is working fine.

The comments to this entry are closed.