Can be a problem though because in today's "language rich" environment with hundreds of languages catering to the needs of 10 niche groups not only highly likes to fail gaining significant traction but also risks to lose its main target group.
Re js: That's something I don't see as a problem as long as it's just a back end and not something that triggers changes in Nim itself. In fact additional back ends are a good example for _additional_ features. My only worry there would be that not having an (additional) back end is better than having a half cooked and not long term maintained one (which however seems to not be likely with Nim).
