Indeed, @leorize is completely right from what I understand as well. One thing I'd like to highlight is that I am in the same boat as you, I mainly write high-level applications, GUIs, web applications, games (targeting browsers), CLI utilities etc. So I have very similar concerns.
**I 'm afraid it will take a lot to convince me to bother annotating my types with ``owned``.** I think this is the biggest risk with the `--newruntime`: ecosystem fracture. We will get packages that are compatible with `--newruntime` and those that aren't. There might be a clever solution to this that I'm not seeing but if there isn't then the risk of ecosystem fracture is very real. All this being said, version 1.0 is going to include a GC and `--newruntime` will not be forced on us for that release. The reason that `--newruntime` is being developed so actively is, well, because @Araq will go crazy if he spends 100% of his time fixing bugs exclusively, this is a feature that he's passionate about :) Don't worry, even though I'm not as active in Nim nowadays, I am still using it for personal projects and holding @Araq to the same golden standard I have always held him to.
