Eclipse Community Forums: Dirigible

Home » Eclipse Projects » Dirigible » Node.js vs J2V8(Node.js vs J2V8 Discussion)

Sat, 06 May 2017 10:24

Eclipse User

Hi Team,

V8 engine seems the most prominent JavaScript engine nowadays, which can be further developed and supported. We have to revise our past decision to rely on the Mozilla Rhino and Nashorn - both JVM based engines.
The major question here is whether to embed V8 engine via the J2V8 bridge https://github.com/eclipsesource/J2V8 or to use directly Node.js

The aspect to be considered:

Maturity and Support
Single vs. Multi Threading
Java components integrations
Debugging support
Programming model - sync vs async
Updates/Upgrades

Regards,
Nedelcho

Re: Node.js vs J2V8 [message #1763435 is a reply to message #1761097]

Tue, 16 May 2017 03:16

Eclipse User

Based on the research and PoC by Dimitar https://bugs.eclipse.org/bugs/show_bug.cgi?id=481644 it seems J2V8 is not a viable option for our use-cases.
In case we want to use V8 we have to go directly to Node.js

Re: Node.js vs J2V8 [message #1763436 is a reply to message #1763435]

Tue, 16 May 2017 03:18

Eclipse User

Re: Node.js vs J2V8 [message #1764246 is a reply to message #1761097]

Sat, 27 May 2017 05:08

Eclipse User

Another approach would be to accept the limitations and to go only for facades in Java with static methods with primitive arguments.
Shall this be enough?
Should we still keep Rhino/Nashorn?

Previous Topic:	Plan Version 3
Next Topic:	Kafka as a Messaging Hub

Goto Forum:

-=] Back to Top [=-

Current Time: Tue May 20 07:12:18 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter