> (a system language? A do a bit of everything language? The cool new web > thingy, ..?.
Again, the usual problem in those discussions is the featureset: not the fact that multiple targets exist. It's perfectly ok to describe Nim as a system language (and still have a good web story), or to describe it as a multi-purpose language (usable for system stuff, applications and browser-based code). However we also shouldn't tap it into only one niche, if it can become a very good alternative of both GC-level "application/sometimes half-system" languages like Go/C#/Java and of actual system languages
