Subj : Re: Menushell.js
To : Nightfox
From : Tracker1
Date : Wed Aug 26 2020 12:14 pm
On 8/24/2020 9:19 PM, Nightfox wrote:
>> Ah, cool. I might take a look at v8 again, but I'm planning to update to
>> the latest SpiderMonkey at some point, which is expected to be painful.
>
> I think the main appeal of Google's V8 engine was that it was supposed to be very fast. But for something that's embedded into the apps we were using, I think Mozilla's JS engine was plenty fast. What benefit do you think there would be to using Google's V8 JS engine over Mozilla's JS engine with Synchronet?
Less of an issue for Synchronet, but a lot of devs and admins aren't a
fan of V8 because of it's complex build system. It's a major reason why
PostgreSQL's plv8 is being dropped (lack of distro support) where
libmozjs is relatively widely supported. They also tend to break their
API a *LOT* which is why even Node is creating their own API abstraction
to make it easier to develop compiled modules against.
As to performance, Spidermonkey is mostly on par with V8 these days,
there may be a little back and forth though. For Synchronet there's
probably not much reason to switch. And there's too much code surface
to do a paradigm shift (such as using Node as the core).
Being able to use some of the more modern language features (and some
bits in-browser) would potentially be nice to have. Async functions in
the non-interactive areas/services could be nice as well.
Aside: been following Enigma development, but other than a simple setup
a couple times haven't really dug in.
--
Michael J. Ryan
tracker1 +o Roughneck BBS
---
� Synchronet � Roughneck BBS - coming back 2/2/20
