> I also think that the killer feature would be a python2Nim converter which > works right out of the box.
That's a two-edged sword... I've been pitching a closer Nim-Python relationship for a while now, but it's also important to maintain some boundaries. We want to attract Python developers into Nim's ecosystem, but Python should never become a dependency for normal Nim development. > While this may be true for Go I think this is not true with Rust. Yes, I didn't want to tweak the quote too much. I find Rust repulsive just from its syntax. > Ideally, I'd like to get a REPL based on Jupyter (formerly known as ipython). That would mean Python becomes an essential dependency for Nim development. I'm sure Nim can come up with a stand-alone feature-rich REPL, and **_optional_** Jupyter integration. > In particular I find the Aporia editor really easy on the eyes, makes it fun > to get coding and tinkering and learning. I like Atom's Nim package. I think it offers everything Aporia does (someone correct me if I'm wrong), plus all the hackability and package ecosystem of Atom.
