VG
And it's not a JavaScript
It's compatible derivative.
Size: a a a
2019 July 17
MV
quickjs is just js to c (or binary) compiler
I compiled the pi.js from examples with
qjsc -e and obtained this result: https://gist.github.com/michaelvoronov/ea513bb8fbea454ec389a0a6e8e4a47e#file-quickjs_pi-c-L164. So, it seems that more precise, to say that quickjs translates js to some special bytecode format (https://github.com/ldarren/QuickJS/blob/5c9d67e87abd127266a92e7787df922f44b895e9/quickjs-opcode.h#L67), embeds it into C file that includes engine libs and calls js_std_eval_binary in main. In its way, this function interprets instruction by instruction (you can find the source code in JS_CallInternal function of quickjs.c).ҪҸ
so quick.js is an interpreter
MV
And yes, there is no JIT
MV
so quick.js is an interpreter
+1
ҪҸ
> Can compile Javascript sources to executables with no external dependency.
that means that it compiles to bytecode + interpreter and not c
that means that it compiles to bytecode + interpreter and not c
P
jsc.exe is installed by default in your Windows since Vista. It was one if three default .NET languages before Core.
I didn't know that, I thought it was c++/CLI c# vb.net and asp.net and then f#, have you ever used jscript.net?
P
And it's not a JavaScript
oh, sad story
P
> Can compile Javascript sources to executables with no external dependency.
that means that it compiles to bytecode + interpreter and not c
that means that it compiles to bytecode + interpreter and not c
your interpretation is strange to me
P
it compiles to bytecode and needs a small runtime to execute it
P
the runtime isn't an interpreter
P
the resulting is a c code that you can compile to binary
P
beating v8 in execution
P
with v8 is difficult to achieve in the same way
P
and the same with node
P
with node you can compile v8 and nodejs std together with the js file but it's in plain js
P
not bytecode
P
it isn't a transpiler
P
if you meant that
MV
beating v8 in execution
by speed?