Question 1

How do I compile JavaScript to bytecode with MQuickJS?

Accepted Answer

Use the mqjs tool with the -o option, e.g., './mqjs -o output.bin script.js', to generate bytecode that can be saved to ROM and executed later with the -b flag, as shown in the REPL section.

Question 2

MQuickJS vs QuickJS: which one should I use?

Accepted Answer

MQuickJS is optimized for embedded systems with ultra-low memory (10 kB RAM), while QuickJS offers full JavaScript support for general use. Choose MQuickJS only if memory is critically constrained; otherwise, QuickJS provides more features and ease.

Question 3

Can MQuickJS run ES6 arrow functions or async/await?

Accepted Answer

No, MQuickJS only supports a subset of ES5, so modern ES6+ features like arrow functions, classes, and async/await are not available, as outlined in the JavaScript Subset Reference.

Question 4

How to integrate MQuickJS into a C project?

Accepted Answer

Include mquickjs.h, provide a memory buffer with JS_NewContext, and use the C API with careful GC reference handling, as demonstrated in example.c and the C API section.

Question 5

What is the memory footprint for a simple 'Hello World' in MQuickJS?

Accepted Answer

MQuickJS can run with as little as 10 kB of RAM, but actual usage depends on the script. Use the --memory-limit option in mqjs to test and constrain memory consumption for specific applications.

Question 6

Is MQuickJS suitable for real-time systems?

Accepted Answer

It may be, due to deterministic memory allocation and no malloc dependency, but the tracing GC could introduce pauses; performance testing is recommended, as benchmarks like Octane are provided but not tailored for real-time.

MicroQuickJS

What is MicroQuickJS?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions