Why does BeanShell's interpreter re-parse a script on every execution by default?

BeanShell's classic execution model treats each eval() or source() call as interpreting the given script text fresh, walking through and executing its statements directly, rather than first compiling it into some cached, reusable intermediate form the way a JSR223 engine typically does.

This design reflects BeanShell's original goal of being a lightweight, embeddable interpreter prioritizing simplicity and direct Java-syntax compatibility, rather than being architected from the ground up for maximum repeated-execution performance the way a dedicated scripting engine with a compilation and caching layer would be.

The practical consequence is that a script called once, or occasionally, pays a modest, largely irrelevant interpretation cost, while the same script called repeatedly - like once per iteration of a high-volume load test - pays that same cost every single time, which is exactly the scenario where the performance gap versus a caching engine like JSR223's Groovy becomes noticeable.

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.

Webull! Receive free stock by signing up using the link: Webull signup.