So? We do not at all disagree on that. You basically just worded differently what I meant (modulo some minor points like "imperative" vs. "imperative with some functional").
I'm _not_ for relaxing those points. Quite the contrary. I was addressing another question, namely whether fully implementing that basic feature set should be delayed because always a new gadget here, some niche stuff there comes up. My basic line is * clearly and _bindingly_ define what Nim is * implement that. Consistently. Fully (incl. good docu and explanatory material). * make sure there are sound basic tools (e.g. debugging, c conversion,...) and a reasonable choice of tools (e.g. editors) support. In other words: Build a solid and full Nim 1.0 Then - and only then - _additionally_ work on gadgets, additions for niches, etc. Example: (afaik; I don't check twice a week) we still do not have proper full uint64 support. Hell, it's 2019 with 64 bits processors being the normal and instead of getting something as basic as uint64.high(), i.e. consistent integer support, Nim cares about what-not niche stuff. Again: I'm in no position to demand anything. The Nim team can do whatever they feel like and we have to gratefully eat what's served (IF we want to use Nim). But this discussion is about promoting Nim and hence I ask what exactly we are to promote? Plus: How seriously can we ask for a language to be taken (and hence be promoted) if its very developers seem to be often distracted and seem to not fervently strive for whatever-is-Nim-is-defined-to-be v. 1.0 incl. the practical basics? What, for instance, will I respond to someone to whom I try promote Nim when he asks me, why 2, not one but two, Nim IDE projects have been left to rot while one of the typical first questions re. languages is "Is there a good IDE"? And what should I respond when that person follows up asking whether that fact (two disbanded IDE projects) does suggest a tendency in Nim's team? I'm a professional. I earn my living with software development. I simply can't afford to make a bad choice. I - and certainly not only just I - need Nim to have clear contours, to reach 1.0, and to deliver. Similarly we know from concrete experience that developers _need_ a good and complete tool set and good docu helping them to get up to speed and to have a solid reference. I learned a lot from Haxe, another somewhat outside the mainstream language with very high potential. Although it _is_ a good language (in its field) and _does_ have a very attractive feature set (and even was promoted and even hyped for some time) all in all it failed. Why? (imo) (very) poor editor and IDE support, no debugger (outside of Adobe Flash), too One-OS (windows) centric. And I'm honestly sorry to say that Nim might have quite similar problems. We should make sure that Nim isn't one of those projects with ever new ideas and experiments that fails to finish and win the race because it got lost in too many distractions.
