It’s really good as an embedded JS engine. Like let’s say you want to make an iOS app that executed JS. If you use V8 (Node’s JS engine), then you’re app is at a minimum 28M in size just from V8. If you use QuickJS, your app size increases by less than 1M.
On iOS, why wouldn't you use WebKit?
(Genuine question; I'm not an iOS developer.)
I don’t think you can create native bindings in WebKit. You can only interact with something like WKWebView using serializable messages. QuickJS let’s you create native objects and expose them directly to the JS API. QuickJS also let’s you get JS variables natively and control how and when things get executed.
You would use JavaScriptCore, not WebKit.
Ah yea that’s right. Now I remember why we didn’t use JSCore. We had a cross-platform C++ library for both Android and iOS so it was better to use a single JS Engine.