Nope, you'd be right. I wasn't overfond of the language syntax
either, but my particular gripe was with rails more so than mere ruby :).
---Pat
-----Original Message-----
From: Warner Onstine [mailto:[EMAIL PROTECTED]
Sent: Friday, April 22, 2005 11:07 AM
To: Tapestry users
Subject: Re: If we call it Tapestry 4.0, not 3.x, Maybe we would do much
Uhh, forgive me if I'm misunderstanding but that would be Ruby on
Rails, not plain Ruby.
-warner (new to Ruby and RoR)
On Apr 22, 2005, at 10:54 AM, Patrick Casey wrote:
>
> Ick, Ruby! I downloaded the tutorial on that one, set up two tables,
> joined them, and printed a list of 1,000 rows that included columns
> from
> each table.
>
> Nine seconds and 1,001 SQL statements later I got my list :). Sorry,
> but anything which uses an N+1 fetch method to resolve joins in
> situations
> like that is a non starter for a serious commercial app.
>
> --- Pat
>
> -----Original Message-----
> From: Jamie [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 22, 2005 8:52 AM
> To: Tapestry users
> Subject: Re: If we call it Tapestry 4.0, not 3.x, Maybe we would do
> much
>
> Once we're all programming in Ruby, we won't have to argue about those
> awful braces that should always open at the end of the line.
>
> ;-)
>
> Jamie
>
> PS and javadoc comments shouldn't have a blank line after them! It
> makes
> them look like they belong to the code above (breaks the proximity rule
> of layout). :-D
>
> <snip>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
