3 ms·

whats the use case of quick js compared to node?

• atwood22 4y ago
  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.
  • skybrian 4y ago
    On iOS, why wouldn't you use WebKit? (Genuine question; I'm not an iOS developer.)
    • atwood22 4y ago
      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.
      • deleted 4y ago
        [deleted]
      • saurik 4y ago
        You would use JavaScriptCore, not WebKit.
        • atwood22 4y ago
          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.
• k__ 4y ago
  Scripting. Like Lua in games etc.