Considerations for choosing NodeBase instead of J2V8?

[aschrijver]

This is a follow-up to #2

For my stackoverflow question on 4 possible solutions, I receive an answer from the NodeBase creator, basically stating that his project is a 'plaything' and J2V8 the best approach.

To me J2V8 (created by @irbull) looks like the most stable implementation currently, leading to my question: Why did you opt for NodeBase?

It seems to me with J2V8 you'd gain:

• a much more active project
• support for newer Node versions (currently 7.6.0, but 8.x just PR'ed)
• additional features:
  • 2-way js-to-java bridge (call java from script and vice versa)
  • 2-way integrated error / exception handling
  • chrome debugging support
  • full build environment with docker-based cross-compile for unix, mac, windows and android
  • more smaller stuff ...

[staltz]

Why did you opt for NodeBase?

Because it solved my problem.

support for newer Node versions (currently 7.6.0, but 8.x just PR'ed)

Actually we can do a lot even with older versions of node.js. Note that Node v6 is currently the LTS.

a much more active project

See above.

2-way js-to-java bridge (call java from script and vice versa)

We don't need this

2-way integrated error / exception handling

We can get errors into the adb logcat, that seems enough to me.

chrome debugging support

That would be nice.

[aschrijver]

Thank you!

[teaserbot]

j2v8 looks good for combine!!

[teaserbot]

saves time building this 😃

j2v8 build 岩 !
:)

[aschrijver]

thanks @teaserbot

[teaserbot]

like eclipsesource/J2V8#335 also
you project lead? or @irbull