review meeting
community
- 28 unique contributors
- 452 starts
- 65 forks
- over 15 persons idling on irc
- ~111 downloads/month over the last year
- 1208 pageviews / 498 unique users
community
people are
using it
in production
community
downstream
- maven-coffeescript-plugin
- jasmine-jvm
- nodyn
- vertx
testimonies
Yay, I was surprised with the fast turnaround for getting my patch accepted!
This codebase is way cleaner than Rhino's
I don't want to fiddle with mercurial
user requests
I'm using it for server-side processing of JavaScript templates, can I run it on JDK6?
competitive
disadvantages
5+ FTE
with compiler experience
we can
catch up
given dedicated effort
comparing
apples
to
oranges
memory footprint
- Nashorn
- Average 35 MiB
- Max 200 MiB
- DynJS IR+JIT
- Average 57.4 MiB
- Max 152 MiB
- DynJS IR
- Average 39.3 MiB
- Max 114 MiB
- DynJS interp (old)
- Average 70.7 MiB
- Max 210 MiB
there are
known
optimization opportunities
full time funding
improves
- nodyn and our node.js story at Red Hat
- vertx's dynjs support
- community projects depending on DynJS
part time funding
keeps alive
- nodyn and our node.js story at Red Hat
- vertx's dynjs support
- community projects depending on DynJS
funding cut
limits
- our community presence
- nodyn goes nashorn?
- we lose control of the runtime
- our server-side JS story