A few of questions and comments for the Cylons :-) 1\. Do you have a (tentative) timeline, particularly for IC support? BTW I really like the idea of porting back IC to 1.6 to let people benefit from it without the potential issues of migrating to 2.0.
2\. Will editor plugin authors need to do something to benefit from the nimsuggest improvements coming from the introduction of IC? 3\. Have you considered introducing the concept of “epochs” (a-la Rust) to make it easier to introduce these kinds of backwards compatibility breaks? 4\. I really enjoy the “batteries included” side of Python. This is not as important in nim thanks to nimble but having a curated / recommended list of community packages becomes even more important if you take stuff off the stdlib. 5\. I’ve read a lot on this forum about simplifying the stdlib and moving things to external modules but what about simplifying the gc story? How many “gc” modes are there and are they all still needed now that arc/orc exist? I guess maintaining all of those modes must have a non trivial cost… Also IMHO this is one of the most confusing / concerning things on the nim “ecosystem”, particularly if you come from a “low level” programming background where “garbage collection” is considered a no-no by a lot of people. In fact, should this still be called “gc”? My understanding is that arc is as much a garbage collector as shared_pointers are in C++. Maybe the --gc flag should be renamed to something less controversial and neutral that does not turn off people coming from a C background…
