> I think it's a mistake to chase every feature it has when we are so early to > a 1.0 release
I don't know what Araq's plans are, but I never thought that this was a 1.0 feature? I thought we were just discussing the idea as a valid RFC to put on the roadmap. I agree that getting 1.0 finished is more important than this. > We need to distinguish ourselves from Rust, not copy its every feature. Rust > definitely does not work like this RFC, it would very much be a > distinguishing feature from Rust. I never implied that we should be copying every Rust feature, and I don't think anybody else has in this thread either. I do believe in stealing the best parts of other ecosytems, but nobody is advocating for a whole sale copy of Rust or any other language. > A GC and exceptions are familiar to us. Nim has a lot of things that are different from Python, such as macros and static typing. Does that mean we should not pursue alternative features just because they are not familiar to a Python audience? > As a fast statically-typed and highly portable Python. I disagree with this, there is already cython and the like. But hopefully we can live together anyway. I actually think Nim can be a language that makes us both happy :-P > Nim is running in your browser and communicating with a server that is also > written in Nim. This is an awesome feature. It is definitely something I love about Nim. I don't want to take that away. In fact, I want to take it to the next step: Nim in the browser communicating with a server written in Nim that is running on an operating system written in Nim. Nim is the only language I've seen that has been able to reasonably extend that far across a tech stack while still maintaining sane syntax and semantics. I want to keep pushing in that direction. I know it won't happen overnight, I don't think anybody expects that. But I do think it's an important goal to pursue. The Destructor runtime is the other big example in this same vein. It is not a copy of another language feature, but more like a hybrid of C++ and Rust. It's a unique feature and It's the best of both worlds in my opinion. It allows Nim to be used for more use cases, like writing shared libraries that can interact with other languages much easier, or writing lower level systems code, while not changing the semantics of the language so much that it can't be used for the current use cases. The GC isn't going away either. The GC is still there if you want or need it. This RFC feels very much in the same vein, or at least I think we can have a compromise that gets us there.
