Could you clarify what "smacks" of a language that isn't very mature? There are libraries written in any language that are not tuned for performance. ("Smacks"

Could you clarify what "smacks" of a language that isn't very mature? There are libraries written in any language that are not tuned for performance. ("Smacks" isn't meant to be pejorative, I guess it's just a British idiom. I just meant "appears to be" or "comes across as") Sure -- to clarify, I think reflection is a pretty important language feature, but it sounds like it's unnecessarily slow on the native target and not really usable on the JS target. It wasn't clear to me whether this JSON parser was a widely-used core library, or just a random third-party one. But a good fast strongly-typed JSON I/O library also seems like something a good new general-purpose programming language ought to have. Maybe it's unfair to extrapolate so much from this one example, but I hardly hear anything about Dart at all. I was interested to see what I assumed was a Dart advocacy post show up on HN, but on reading it, found it didn't make Dart sound very appealing. > why would I choose Dart over Go? I don't know. Why do you have to choose Dart over Go? I'm not trying to start a language war (I kind of picked Go at random, mostly because it was also started by Google). But I think it's a reasonable question, and there's room for a bit of advocacy here. If people like Dart, what do they like about it?