Mine as well.  I use BeanShell in a production environment for years and am also worried about its "support".
Not that I'm expecting free labor, or even active development by volunteers,
but it is worrisome that known bugs or future bugs may bite me.
I do have the source so I could fix things myself, but its a bit unsettling.
I like the idea of the beanshell2 fork on google, and have contibuted to it in the past.
But the goals of that branch differ from mine ... or atleast *may* differ in the future.
I dont want enhancements, or refactoring of the code, simply stability and possible extreme bug fixes.
But again, I'm not expecting someone else to do my job.   But also I dont want my job to be bug fixing an existing library either !:)
 
I'm considering shifting over to "pure java" by natively invoking the javac compiler, loading the .class files and executing them
with reflection.   The syntax wont be as nice, and its a non-trivial job to implement this, but in the long run it might be a better
architecture then relying on an 'abandoned' platform no matter how good that is.
 
 
 
 
 
----- Original Message -----
From: Gary Furash
To: Beanshell-developers@lists.sourceforge.net
Sent: Tuesday, December 09, 2008 12:53 AM
Subject: Re: [Beanshell-dev] Status of project and adding 1.5 generics

Your experience. matches my own.  Groovy became its own language.  Beanshell as really an ideal scripting language.  We used it extensively at my old shop and it held up beautifully.  Pat did a great job and then had to move on for whatever reason.

On Mon, Dec 8, 2008 at 6:51 PM, Paul Reavis <paul@partnersoft.com> wrote:

On Dec 8, 2008, at 7:42 PM, Paul Landes wrote:

> Is there anyone attached to beanshell for JDE critical functionality?
> Again, I'm a huge fan of it, but not if it isn't maintained.

We use it extensively at Partner Software. It's the primary scripting
language for our platform (a sort of gis viewer on steroids with
accompanying application server).

I have been concerned about beanshell's lack of support for some time.
We originally used Jython (back when it was the only scripting
language for Java), then played with Groovy, and finally settled on
BeanShell. My primary requirement was that it be more or less
syntactically identical to Java, so that I could easily port code to
and from Java, and so that people starting in scripting could migrate
to "real" Java development without too much change shock.

Jython was adrift for awhile but now seems actively maintained. I have
no problem with Jython or Python per se but I find it difficult to go
back and forth between it and Java - they are syntactically close
enough to make it easy to screw up.

I liked Groovy initially but it started wandering off weirdly for
awhile, then they made the decision to make it very different from
Java so I lost interest.

I have cracked open the BeanShell code and fixed some of the issues.
It's not terribly well written and has some modularity issues; I had
to hack in some support for a sort of compile-once-run-often model to
improve performance - our system tends to have lots of small scripts
that get executed often. And as others have mentioned it would be nice
to get 1.5 and 1.6 features in. I did add vararg support though it's
not perfect.

Nowadays there are any number of scripting languages one can code in;
I've made the support in our platform modular so it supports bison,
jython, jruby, beanshell, stringtemplate and pretty much any other
implementation of the Java scripting framework or even custom ones if
you can implement a simple interface. But I still like the idea of a
very Java-like scripting language.

Considering our investment in it so far, I would be willing to adopt
the project and work on getting a new version out, especially with
those fixes I feel need to be in there. I don't have tons of time,
however, and I can't guarantee that I would push the code very
aggressively. By and large it works well for us. My goals would be:
1) stability
2) performance
3) adherence to Java syntax wherever possible

I am not at all interested in custom syntax, extension frameworks like
Grails, etc.

And with all due respect to Pat, I've always thought the name was silly.



------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/beanshell-developers



--
Gary Furash, 602-561-9057, furashg@alumni.bowdoin.edu


------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/beanshell-developers