> | 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.
Actually it doesn´t mean
IMHO Nim doesn't need any new features to move to 1.0. Just general tidying and
bug fixing. Maybe moving some features to __future__.
A little off topic but I've tried Nim in a lot of different editors. I tried
Visual Studio Code for the first time as an editor to see what the Nim
experience
> 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
I'm not a particularly good programmer, but I'm loving Nim for how easy it is
to get started working with it. In particular I find the Aporia editor really
easy on the eyes, makes it fun to get coding and tinkering and learning.
That said, one thing I am missing (and I do recognize I may have
@vega Yes, I did. Unfortunately, it's not feature-rich enough to become the
official Nim REPL. It's rudimentary by definition.
moigagoo, did you try this?
[https://github.com/vegansk/nrpl](https://github.com/vegansk/nrpl)
@Libman: You quote this "...Go and Rust are easier to get started with because
they are simpler languages. ..."
While this may be true for Go I think this is not true with Rust. Rust with its
ownership concept is much harder to learn, IMHO.
I also think that the killer feature would be a python2Nim converter which
works right out of the box. Something like this would help to pull in any
number of developers and presumably sponsors:
import nimNumpy as np
import nimMatplotlib.pyplot as plt
from
For someone used to languages like Python and Go, Nim's kitchen sink approach
can be a bit intimidating.
Quoting [someone's comment from YComb
News](https://news.ycombinator.com/item?id=11959437):
> Nim is great, and I use it (in production), but I know exactly why it isn't
> as popular:
