A core Python committer's (very shallow) thoughts on Dart

<i>Dart views types as helpful documentation and a way to help tools assist with things, period. I actually find it rather refreshing to have a language that treats types as just documentation since that is really what they are for the programmer</i><p>But, just like documentation, if it gets out of date you're really wonked.<p>I'd prefer something that is both useful as documentation <i>and</i> is used by the compiler (a la Haskell's type classes).

Interesting, and very positive review.<p>Maybe it's my Java background coming through, but I <i>like</i> the idea of Factory constructors.

Single-inheritance, but interfaces can have default implementations? Isn't that... multiple inheritance?

<i>they still went a little overboard in my opinion on some things (e.g. the list interface has a last() method instead of supporting negative indexes).</i><p>A last method is much more intention revealing and easier to scan for me than negative indexes.

<i>...have done toy examples now in 18 languages...this is actually usually enough for me to grasp the inspirations for a language and thus understand its essence.</i><p><i>Usually</i> is the dangerous word here. (Dangerous as in, "a little knowledge.")

Some responses from the Dart team: <a href="https://plus.google.com/115362263245161504841/posts/82jKeP4YjbG" rel="nofollow">https://plus.google.com/115362263245161504841/posts/82jKeP4Y...</a>