3 ms·
If you don't mind potentially slow code, that's a fine thing. Once you've measured and discovered that you're losing out on a lot of performance, it's worth eva
by greglindahl 10y ago
If you don't mind potentially slow code, that's a fine thing. Once you've measured and discovered that you're losing out on a lot of performance, it's worth evaluating whether the risk of leaks can be baked away via careful testing, which doesn't appear to have been done at all in the library used in this blog post.
- brianwawok 10y agoWell pure Java code is 10x to 100x faster than pure Python code. So you aren't exactly accepting slowness in that case.
- greglindahl 10y agoIf you say so. That's not what I've observed, especially if you're talking about code where Python is the glue and all the heavy lifting is done in C or C++.
- brianwawok 10y agoI am comparing Java to Python. Not Java to Python code wrapping C++ code. Because in that case, we would be really comparing Java to C++ code. Which I am happy to do, but not what I did.
- greglindahl 10y agoThis whole thread was about memory leaks caused by not sticking to a single language.