Re: [Beanshell-dev] The sad state of Javascripting

Hi Guys,

> On the other hand, why restrict a fork to bug fixes only? I'd be
> tempted
> to implement and experiment with _significant_ new features rather than
> wait for a committee in a closed room to decide what's best for the
> user
> community, as it happens with every other JSR. Correct me if I'm wrong,

OK ;-)  Not all JSRs work that way.  Many open the discussion for comments
from the community at a relatively early stage.  The stage at which this
happens is up to the spec lead.

> we'll all have to hold our breadths and wait and
> hope
> for the best. Take a look at how impressive Perl 6 is in terms of
> linguistict capabilities...it's because it is a product of the whole
> community!  shell-users

Remember that the goal for BeanShell is not to implement every possible
language feature, but to provide what is basically an optionally typed
interpreted version of Java (with a limited number of scripty features.)

If you are looking for Java + a ton of language features you might want to
look at Groovy.  Groovy has very different design goals.

Cheers,
Dan


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/