Well, these things are fun to hack on and then each might solve a part of the generally near-unsolvable problem, and for each such part there are people caring about <i>that</i> part the most so the solution has its uses. (Incidentally, my own preference to date has been to only use CPython and fall back to C extension modules when speed starts to matter... But I could have a different preference in a different environment working on different things.)<p>Kind of like making C or C++ safe is a near-unsolvable problem for most values of &quot;safe&quot; and there&#x27;s an ever-growing set of static and dynamic analysis tools detecting things like uninitialized memory access, out of bounds access, data races, integer overflow, etc. etc. etc. And each of these tools gives you a different mix of false positives, false negatives, build time overhead (including getting the program to build with the tool at all) and runtime overhead (including getting the program to run), not to mention availability on a given platform and pricing. And different people have a different preference with respect to what this mix should be for their tool of choice. But the problem is unsolvable which is why it&#x27;s <i>worth</i> to be &quot;trying everything.&quot;