News for hackers. Stuff that matters.
Re:A core Python committer's (very shallow) thoughts on Dart by nl on Monday May 14, 2012 @11:18AM (#3971400)
I guess... my gut tells me that you should either have types, or not have types. Being in the middle creates too many opportunities for cognitive dissonance, too many opportunities for sneaky bugs, and too many opportunities to keep having this debate. It's one of those things that seems really smart and cool that, on a practical level, will probably turn out to be a complete waste of time and a total distraction.

The worlds collective programming experience doesn't really back that up. Almost every language drops (or makes optional) type support when constructs become too complicated, or they become so complicated no one can understand them.

Languages with the best type systems (OCaml) aren't particularly popular, while languages we think of as strongly typed (eg Java) have big backdoors to allow people to bypass the type system.

On the other side, weakly typed languages are adding typing-like features by integrating unit test facilities into the environment (which - optionally - catch many of the bugs typing can help with).

Like so many things, optional typing might seem impure, but often messy systems are the most robust.

Re:A core Python committer's (very shallow) thoughts on Dart by pcwalton on Monday May 14, 2012 @11:34AM (#3971470)
Dart's optional typing is not common in languages at all. What you're referring to is a combination of dynamic and static typing, which is not Dart-style optional typing. In statically-typed languages, the dynamically-typed values are clearly delimited in the source text and are not a compiler switch.