First of all thank you for all the hard work guys. Much appreciated.
I think Nim reaching 1.0 set many people's expectations very high and now it's time to consider how can the Nim ecosystem thrive.
Topic 1
Memory management seems to be going in the right direction but I fear "ARC" needlessly fractured the small community. It's a bit unsettling that a lot of pkgs do not work with ARC at all. And these are very essential things like parsers,db drivers etc.
eg https://github.com/nim-lang/Nim/issues/14020 parsers relying on deep copy https://github.com/nim-lang/Nim/issues/13997
Topic 2
Important packages is a very good approach but it needs to be expanded. Important packages simply cannot break with every other release of Nim.
Topic 3
Missing / abandoned important packages. At the moment Nim does not really have a usable,production ready, http server package. I know it's hard I cant do it myself and therefore rely on others. This is I think important to get done.
Topic 4
This is maybe non technical but features that do not really "work" or are not really "maintained" should be marked as "experimental" or with some visible warning.
3. I'd argue that Jester (and it's underlying httpbeast) are mostly production-ready
Yeah. You're all using it right now through this forum, been running in prod for years.
Memory management seems to be going in the right direction but I fear "ARC" needlessly fractured the small community
A lot of implication here that ARC is going to be the new default. While this may happen, it's far from certain, and even if it does it won't be until Nim 2.0. So there is no ecosystem split here, unless you desperately need ARC for something.
It's a bit unsettling that a lot of pkgs do not work with ARC at all. And these are very essential things like parsers,db drivers etc.
ARC is new while the old GCs had years to mature.
That said, the main use-case for ARC beyond embedded, multithreading, doesn't work because of a regression in exception handling + Arc but fixes are in progress: