From: Marcin Raczkowski <mailing.mr@...>
Date: 2007-10-02T02:38:56+09:00
Subject: Re: Ruby vs. PHP

> Well no not really. The last really good writeup on the internal workings
> of google, came from Steve Yegge a couple of months ago (see his
> blog on Rhino on Rails).

I heard they are STARTING to use ruby from one of google employes.

> 
> I am not being hypercritical of your choices. In your situation, I would go
> with Rails over PHP as well, for much of the same reasons (performs
> well enough, rapid delivery, long term maintenance).
> 
> But you have committed to an ActiveRecord rewrite, and your reasoning
> is not clear. It sounds like you have read something that 'ActiveRecord
> doesn't scale' without investigating thoroughly.

I didn't "hear" anything, i performed tests and benchmarks, with few 
ORMs (AR, Og, sequel) and pure postgres library and obviously pure hand 
made SQL is best - of course i can use AR's find_by_sql, and sometimes i 
do but it's slower then pure call.

personally i never had to use pure postgres driver except for one small 
script that was loading xml to database(where switching from AR to 
postgres driver changed execution time from 12 min into 7 min)

> 
> Rails gets a lot of its productivity from ActiveRecord. By getting rid of it,
> you lose that, and you also close the door on the community development
> of ActiveRecord and its supporting plugins.
> 


I'm planning to use ORM, and use pure sql for most frequent calls (like 
checking for new messages, or new stories) that are made by ajax