STPyV8 – Python3 and JavaScript Interop with V8

Re:STPyV8 – Python3 and JavaScript Interop with V8 by rvz on Tuesday December 31, 2019 @07:15PM (#21925729)

> Other uses include squeezing in some "bare-metal" hyper-optimized (by V8) JavaScript into your Python projects, say as a stepping-stone to a full node.js port.

So we resort to having a double GC where one GC is present in Python and another one is in V8 which by reading this "use-case" sounds pretty strange for "bare-metal" applications which begs the question: Why?

There's a reason the deno project switched from Go to Rust to eliminate this problem and I don't see why using this library with Python + V8 for this type of use-case would make any sense.

[ Parent | on HN ]

Re:STPyV8 – Python3 and JavaScript Interop with V8 by randomfool on Wednesday January 01, 2020 @12:11AM (#21926755)

Not just an issue for ‘bare metal’ applications- two GCs will be difficult for more complex scenarios as well where objects will have longer lifetimes spanning VMs.

This is a cool project that can definitely be useful, but those GC issues could rise up if you try a complex project and don’t design for them.

[ Parent | on HN ]

Re:STPyV8 – Python3 and JavaScript Interop with V8 by amelius on Tuesday December 31, 2019 @09:36PM (#21926288)

Probably because a GC is tightly coupled to the runtime system of a language, and using a different GC requires rewriting the entire interpreter.

[ Parent | on HN ]