Node.js vs J2V8 [message #1761097] |
Sat, 06 May 2017 14:24 ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
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 #1764246 is a reply to message #1761097] |
Sat, 27 May 2017 09:08 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
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?
|
|
|
Powered by
FUDForum. Page generated in 0.03096 seconds