Sign in through GitHub

Please read for an updated status on RailsCasts:

Learn more or hide this

Boris Brodski's Profile

GitHub User: borisbrodski

Site: http://sevenzipjbind.sourceforge.net/

Comments by Boris Brodski

Avatar

Thanks for the great screencast!

When it turns to such things as DRY concept between Server <-> Client, I think about DSLs. Ruby is a great language for embedded DSLs, so why not to write a new DSL to write (for example) validation code with and then generate and execute from that DSL-code:
- Ruby no the server side
- JS on the client side

This DSL could be exandable by rails apps to allow any complexy operation. On the other hand, such DSL could also provide the natural limitations to users. For example, you can't ready access dom attributes or data base from such "DRY" code.

What are you think?