@cdome There is a point in discussing this now, otherwise we will end up with something unsatisfactory in 2020. The post by @GordonBGood \- while having problems with the benchmark, as pointed out by @Jehan \- discusses some shortcomings of the new runtime that are worth debating for me.
The issues that I see are: * supporting both runtimes will make the stdlib more complex and brittle, and less understandable * the new runtime does not seem to bring many advantages wrt multithreading, which is the current biggest limitation * not everyone comes from a C/C++/Rust background. Most programmers are used to having a GC, and an alternative mechanism makes a **huge** impact in how Nim is perceived Apart from this, I have a question for @Jehan: you say > The main cost of naive reference counting comes from assigning pointers to > local variables (including argument passing) Isn't this problem solved by having **deferred** reference counting?
