Re: BeanShell alternatives (was Re: Status of projectand adding 1.5 generics)

David A. Lee wrote:
> 
> So not only is BSH alive and well ... but its being continued in new 
> projects .. atleast in my shop.
> 

Mine too.  Here is a nice one we developed recently
http://code.google.com/p/plbsh/ .  It lets you run BeanShell in Postgres.



> Given that I would LOVE some kind of semi-active semi-official handover of 
> the codebase to dedicated maintainers, and volunteer to be one of them.
> the beanshell2 google fork is a good thing, I have contributed to it in
> the 
> past, but I think its goals are different then what I suggest.  I suggest
> a 
> fork who's #1 main goal is stability and minimum changes.  Bug fixes only 
> ... and MAYBE a path towards new java syntax support ... but not new 
> features, and heavily focused on maintaining legacy use.  I think thats a 
> fundamentally different goal then a "new and better beanshell" which is
> also 
> a good goal ... but not the one I'm most interested in personally.
> 

I think this is an important discussion to have.  We should be able to agree
on something that is usable by everyone.  My view is that avoiding changes
and enhancement will make BeanShell a dead end eventually as other scripting
languages add features that people want.  The important thing to preserve in
BeanShell is Java compatibility.  This cannot be compromised, as it has been
in Groovy.  But adding new features is fine as long as strict Java code
continues to work properly.  No one has to use the extra features.



> To achieve this goal I suspect will require some kind of "committee" so
> that no 
> individual is tempted to make changes without consensus or oversight.  Of 
> course that slows things down and is inefficient ... but then that's the 
> point.
> 

A programmer who wants a new feature will just add it to his copy of
BeanShell.  If the common code is regulated by a bureaucracy, the programmer
won't bother dealing with it to submit his changes.  For BeanShell2, this is
my policy:

"Please create an issue (on the Issues tab) before changing code. When
committing code, refer to the issue in the comment. If the issue is a bug
(defect), you can fix it right away. If the issue is an enhancement, please
wait 24 hours for comments. If no one objects, then you can implement the
enhancement."

Even with this simple system, I get virtually no contributions.

-- 
View this message in context: http://www.nabble.com/Status-of-project-and-adding-1.5-generics-tp20860930p20944725.html
Sent from the BeanShell - Dev mailing list archive at Nabble.com.


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/