Honestly, I looked into it and couldn't figure out what all the fuss
is about. For a little toy crud application it's nice and fast, but, hey,
so's python, perl, or PHP.
It just doesn't have to features I'd need to build what I consider a
"real" application. One question in the rails forum kind of told me
everything I needed to know.
"So, how would I use rails to run a specific task on a repeating
schedule".
"What, like a scheduler?"
"Yes, exactly like a scheduler. I need to scavenge flagged deletes
in the background so that foreground performance doesn't have to suffer."
"Well, umm, you could write a cron job ..."
I was deleting Rails off my machine within the hour. There were
other issues as well, but some of them at least seem to have been resolved
since then (the n+1 selects problem has been solved for example).
--- Pat
> -----Original Message-----
> From: Cosmin Bucur [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 08, 2005 12:15 PM
> To: Tapestry users
> Subject: Re: tapestry to JSF conversion
>
> since we're discussing efficient development with .net , i thought i'd
> shoot the question ummm ....
>
> what do you guys think of Ruby on Rails ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
