In the strictest terms, I think you're right, but that's primarily just because it hasn't yet reached 1.0. Both Go and Angular have been 1.0+ for quite some tim

In the strictest terms, I think you're right, but that's primarily just because it hasn't yet reached 1.0. Both Go and Angular have been 1.0+ for quite some time, so it's not really a fair comparison. While I'm impressed with Go, I personally find Dart far more accessible. Because of my Java background it makes a lot more intuitive sense, and its target user-group is web developers. Go has an immense amount of power for the same group, but unfortunately it's marketed as a system-level language (which I understand it does very well, but isn't of interest to me) and is similarly inaccessible. If Go focused more on presenting itself (particularly in the tutorials/learning aids area) as a language for web development, I think it'd stand an excellent chance of stealing market (and mind) share from Node, and possibly even Dart on the server-side. It's possible they will pursue this course in the future as it has become quite obvious that their intended user-group (C++/low-level guys) aren't generally that interested in a replacement language. Like many others who've kept Dart on their radar, I've been waiting to get serious about Dart until it stabilized at 1.0. Now that its 1.0 release is imminent, I'm likely to move into Dart in a big way. JS is fine and works very well for a lot of folks, but Dart is much more appealing (a lot more sane) to me. I suspect when it's been post-1.0 as long as Go and Angular it'll be as popular. In other words, give it a year or two.