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

>> I feel that the first step in Leading an offshoot of Beanshell is to make
>> and achieve agreement on a list of bugs to be fixed in the base of the
>> offshoot.
>>
>
> Why?  If everyone would just fix whatever bugs bother them in a common
> source repository, then we would all benefit.  This is why I set up
> BeanShell2.  Whenever I run into a bug that affects me, I fix it there.  I
> wish others would do the same.

Because with something like beanshell there is no formal specification.
That means one person's bug is anothers feature.   In  a program like 
beanshell,
its current implementation is the 'defacto standard'.

Certianly there are a class of bugs that we all would agree are truely bugs,
but I suggest there is a huge wider range of "things I think are wrong" that 
others would disagree.
For some programs and people thats fine for others it is not.
For example, I would stop using Java or C if anyone who thought there was a 
"bug" decided to "fix" it.

There's good reasons for annoying painful slow beuracracies ... especially 
when the original innovator is no longer participating.




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