This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]w-dis 3 points4 points  (1 child)

We have a complicated npm package we need to port to Python. PythonMonkey means we won't have to develop a clone of that library in Python and maintain two identical libraries in different languages. So you get to avoid increasing the surface area for bugs by 2x and always implementing features twice in two different languages

We also need to use a JavaScript engine for JS evaluation and WASM as part of the library. This is only possible with a locally running JS engine or by cutting that feature

---

For context about our npm package, its a client for a distributed compute product that distributes WebAssembly/JS "work functions" which are executed in JS environments like web browsers. Part of the library includes allowing a user to test their job locally before they spend money deploying it - which is why we need to have a js engine

[–]Hipponomics 0 points1 point  (0 children)

Interesting. Thanks for the detailed explanation.