il Tue, 29 Jul 2003 02:06:48 +0900, Armin Roehrl <armin / xss.de> ha
scritto::


my 2c:
they won't let java. 
Not soon at least.

So you should'nt try to show them how you can replace java, but how
ruby can help java development. 
BTW, with time, they'll notice that ruby is the best thing since
sliced bread and move theyr focus on it.

So, what to show?

- ruby as a tool generator 
 ( automating builds, automating tests, or better automating test  
   generation..)

- ruby as a code generator 
 ( sql/javacode/xml_deployment_files and so on from stubs..
   hey did I see a book related to this here? ;) 

- ruby as an embeddable domain language
 ( show DataVision , using JRuby scripts 
   to keep details out of the main abstraction.
   PragProg's stuff for more on this point )

- ruby as a prototype language 
 ( DAO strategies via open classes, iterators and so on goes here)

- ruby for one-time operations
 ( such as adding that old COBOL record file to your new ORDBMS..
   regexp and File,IO goes here)

- maybe, ruby for mock components, via JRuby or in the case of
client/server stuff for one of the two