On Tuesday 25 May 2004 06:10, J Aaron Farr wrote: > Niclas Hedhman wrote: > > I will check out groovy. > > The near-term plan is to support more plugin types. First step is to > > allow the BSH ScriptFacade to re-use the compiled Java code instead of > > the plugin script files, since a class file is always compiled when a > > Plugin is installed. > > Then allow for 'pure Java' plugins, and then perhaps add support > > additional scripting types. Object-Orientation is a requirement though, > > so some scripting is more or less out of the question. > > Why not use BSF? > > http://jakarta.apache.org/bsf/index.html > > Then we can use all sorts of scripting languages. Whatever someone wants.
Reason for choosing Beanshell over BSF; * In BSF does not require OO. * The BSF bridge between Java and the script is very weak. * In BSF it is far from trivial to have snippets in one plugin call code in another snippet/plugin. The beauty of BeanShell makes every Plugin snippet a real Java class, in fact it is an Avalon component, and the Plugin Plugin does compile time checks when plugins are installed to help the plugin developer with syntax errors. A next natural step is that plugins script snippets can be loaded as native classes, to possibly speed things up even more. Furthermore, introduction of BSF and massive handling to make various scripting languages work together, will only slow things down. I think you (and Jason van Zyl) is struck be Flexibility Syndrome. Just because it can be done, doesn't mean it should. Everyone in the Java community knows how to code Java, by definition. Why even bother with other languages? That was my initial stance at the whole build issue, together with; "Should builds really be declarative?" which used to be the basis of Ant. Adding additional languages, just limits the number of people who can or want to participate in the project, and makes transitions to 'younger blood' so much harder. IMNSHO, allowing for many scripting languages, which is the route that JvZ makes in Maven2, is a receipe of disaster, a matter of diluting already thin resources, on the same basis as Avalon was having 4+ containers to support. SoC's first principle; Do one thing only, but do it well. Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
