On another thread @carterza [commented](https://forum.nim-lang.org/t/8613#56032) that he was unsure of the direction of Nim and unenthusiastic about the effect system and enhancements to it, and that he'd be more interested in half baked features (concepts) being made solid and less used features being deprecated. Multimethods are deprecated, maybe the effect system should follow, if it's a productivity killer.
I share his concerns. I like Nim a lot, but I'm also unsure of its' direction. My interest is Nim as a systems programming language. It would "compete" with C, C++, and Rust. No required tracing GC and no need for a D-like DasBetterC. The ability to interface with existing C++ code is a "killer feature" for me. I also see Nim being used as a high performance scientific computing language; again, competing with C++. IMO, a lot of the effort to make Nim a web development language is pissing in the wind. What are the plans for Nim? I know incremental compilation is desired, and looking at [PRs](https://github.com/nim-lang/Nim/pull/18818), I see that solutions for cyclic module dependencies may be in sight. Will we see significant deprecations in Nim 2.0? When is that expected to happen? Sorry for rambling. I'd prefer not to see Nim play out as D has.
