Thomas Fuchs wrote:
> You still get all the underlying interfaces (SQL for Activerecord,
> Javascript for RJS), so you can have the best of both worlds, as
> opposed to both having a strict layering that's favoured by some of
> the "enterprisey" frameworks out there, or the other "extreme" of
> hand-coding everything.
Thanks; now lets try saying it like this:
- pick a core language for your app. For example, if you team
has not yet bought the TCO for stored procedures, don't
be the one to start
- write in the core language by default, without a defensible
reason to use one of the peripheral languages
- if the core language comes with generators for code in
the peripheral language, use them to learn that language,
and possibly to apply tweaks
That rationale applies equally to Rails and JavaScript as to C and
Assembler. Including disassembling your compiled code to learn what
the compiler did...
--
Phlip
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
