4 ms·

I certainly would be happy to know about it when it comes out! I would rather avoid the double ecosystem in the long run, but it would be a great thing to have

• jboy 11y ago
  I assume you're the article author? If so, I know who you are on the Nim forums, so I'll certainly keep you informed. :) In terms of ecosystems, I think that there is deployed Python code in the world that will never be re-written in Nim. I would prefer that Nim can be used to write drop-in extension modules for this Python code, rather than not at all. I also think that there are situations where Python is a better fit for a problem than Nim. For example, handling JSON files in Nim (or any statically-typed language) will always be awkward (you have the choice between a double-dispatch Visitor Pattern or accessor methods that cast), but in Python, handling JSON is the easiest thing in the world. Likewise for any heterogeneous container. By the way: Great article about Nim, as always. :)