> IMO Nim should drop some features (e.g., method), fix broken stuff that was > documented but not ready (concept, static[T], regions if they're still > there?), and ship a version 1.0. Not, for example, try to develop tooling to > compile to JS, amongst other things. Nim can't take on Typescript, and > shouldn't try.
I absolutely agree that Nim should drop some features, but the question is which? This is something that I don't see us agreeing on. To me the JS backend is essential and I absolutely love it. But yes, either @Araq will make some tough choices, bite the bullet and remove niche features or we won't ever get 1.0.
