QuickJS JavaScript Engine • Hacker News Board

Re: QuickJS JavaScript Engine

#51

Post by mstade » Thu, Jul 11, 2019, 6:06 PM UTC

MuffinFlavored wrote: post #49

exebook wrote: post #30

Earlier quoted context omitted.

fs/net and some other important pieces of Node.js are written as C++ addons for v8, hooking them would be very difficult I guess. Though Microsoft have been working on this for their ChakraCore engine. There was a conflict if I recall correctly, Microsoft suggested to add another abstraction layer to make hooking other JS engines easier but Node.js team refused it. I might not know that situation very well. But I hav…

How could we easily expose syscalls to `qjs`? Deno is just a Rust IPC/syscall layer glued to V8 really...

Some Node APIs could probably be implemented using the std and os modules[1], but others (e.g. networking) would probably need to be implemented via the C API[2].

[1]: https://bellard.org/quickjs/quickjs.html#Standard-library

[2]: https://bellard.org/quickjs/quickjs.html#QuickJS-C-API

Re: QuickJS JavaScript Engine

#52

Post by shsh » Thu, Jul 11, 2019, 6:07 PM UTC

anderspitman wrote: post #43

MuffinFlavored wrote: post #39

Earlier quoted context omitted.

He's probably worth $300-$500/hr if not $1k...

Can you really put a number on this level of skill and productivity?

Yeah... his current employer already does.

Re: QuickJS JavaScript Engine

#53

Post by jerome_k » Thu, Jul 11, 2019, 6:08 PM UTC

mirekrusin wrote: post #36

Is it possible to contribute a patch? How should I do it?

from https://bellard.org ...

If you have any questions or suggestions, write to fabrice at bellard

Re: QuickJS JavaScript Engine

#54

Post by andyfleming » Thu, Jul 11, 2019, 6:09 PM UTC

Will the source of this be published to github (or similar) for contributing?

Re: QuickJS JavaScript Engine

#55

Post by suhail » Thu, Jul 11, 2019, 6:13 PM UTC

quickjs.c is 47,842 lines of non-generated code. :mindblown:

Re: QuickJS JavaScript Engine

#56

Post by MuffinFlavored » Thu, Jul 11, 2019, 6:14 PM UTC

shsh wrote: post #52

anderspitman wrote: post #43

Earlier quoted context omitted.

Can you really put a number on this level of skill and productivity?

Yeah... his current employer already does.

Do you know who his current employer is (if any)?

Re: QuickJS JavaScript Engine

#57

Post by MuffinFlavored » Thu, Jul 11, 2019, 6:15 PM UTC

FiloSottile wrote: post #46

MuffinFlavored wrote: post #39

Earlier quoted context omitted.

He's probably worth $300-$500/hr if not $1k...

That's a pretty standard range for high level consultants. Bellard can definitely bill well above that, if there are tasks that require his talent.

How much higher above $1k/hr can he bill?...

Re: QuickJS JavaScript Engine

#58

Post by kostadin » Thu, Jul 11, 2019, 6:18 PM UTC

The operator overloading is potentially huge. Along with the BigInt/Float extensions, it makes it a great target for scientific computing applications.

Re: QuickJS JavaScript Engine

#59

Post by MuffinFlavored » Thu, Jul 11, 2019, 6:18 PM UTC

mstade wrote: post #51

MuffinFlavored wrote: post #49

Earlier quoted context omitted.

How could we easily expose syscalls to `qjs`? Deno is just a Rust IPC/syscall layer glued to V8 really...

Some Node APIs could probably be implemented using the std and os modules[1], but others (e.g. networking) would probably need to be implemented via the C API[2]. [1]: https://bellard.org/quickjs/quickjs.html#Standard-library [2]: https://bellard.org/quickjs/quickjs.html#QuickJS-C-API

It'd be super neat if he added a native `net` module. Then we could do node.js http/net vs QuickJS benchmarks.

Re: QuickJS JavaScript Engine

#60

Post by minxomat » Thu, Jul 11, 2019, 6:20 PM UTC

mstade wrote: post #20

I just tried building this on my Mac and it looked initially like it all was building fine, but it eventually failed when building qjs32. Thinking this probably didn't matter much I went ahead and ran `./qjs examples/hello.js` which worked as advertised – cool! Tried `./qjsbn examples/pi.js 5` and it worked as well – very cool! Then I tried `./qjs examples/hello_module.js` and got this: SyntaxError: unsupported keywo…

Heads up, I had to unset CONFIG_M32=y on macOS Catalina. There are no headers or symbols for 32bit apps in macOS anymore, so this will exclude the *32 variant targets.