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

I'm in favor of pursuing all possible avenues here.  There is a small community of BeanShell users.  Some of those people are actively listening to this conversation.  The rest are either not on the list or are using BeanShell "under the covers" and may not be aware of what's going on with the project on a daily basis, but might care about eventual outcome at some point in the future.  And of course there may be potential future users.  Why don't we put up a portal page maintaining links to all the BeanShell forks and what each fork's mission statement, version, and maybe status of development is.  Ideally, someone could come to this portal and find a compatibility and feature chart and make an informed decision.  We could even do this on Wikipedia.

Alexey
2001 Honda CBR600F4i (CCS)
1992 Kawasaki EX500
http://azinger.blogspot.com
http://bsheet.sourceforge.net
http://wcollage.sourceforge.net



--- On Thu, 12/11/08, fschmidt <[email protected]> wrote:

> From: fschmidt <[email protected]>
> Subject: Re: [Beanshell-dev] BeanShell alternatives (was Re: Status of projectand adding 1.5 generics)
> To: beanshell-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Date: Thursday, December 11, 2008, 11:10 AM
> David A. Lee wrote:
> > 
> > I disagree that adding new features is fine ... for
> the beanshell that I 
> > want atleast.
> > Thats one reason I'm still at b.04 instead of
> using the beanshell2 base, 
> > even though I know there are good fixes there.  I dont
> know what else is 
> > there and I dont want to spend the time to find out
> for sure.  Ok I admit
> > it 
> > I'm lazy and risk-adverse for this project :)
> > 
> > The core issue, to me,  is risk management.  In the
> ideal world everything 
> > "continues to work properly", but in reality
> it often does not.
> > 
> 
> This is not a new problem.  Every open source project deals
> with this issue. 
> The usual approach is to fork off a new development version
> before making
> major changes.  If someone wants to take responsibility for
> release
> management, he can organize this.  This allows for both
> stability and
> development.
> 
> That said, BeanShell2 does continue to work properly
> because the
> enhancements have been minor.  I challenge anyone here to
> find a new bug
> introduced in BeanShell2, that is a bug in BeanShell2 that
> is not in
> BeanShell.
> 
> 
> 
> > I also disagree that limiting changes to bug fixes
> makes a project dead.
> > 
> 
> Can you think of a single open source project that is
> limited to bug fixes
> that isn't dead?
> 
> -- 
> View this message in context:
> http://www.nabble.com/Status-of-project-and-adding-1.5-generics-tp20860930p20958551.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/
> _______________________________________________
> Beanshell-developers mailing list
> Beanshell-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/beanshell-developers


      

------------------------------------------------------------------------------
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/