Re:Brad Fitzpatrick on the future of Go
by munificent on Tuesday October 14, 2014 @02:28PM
(#8454912)
While I really like Go's approach to concurrency, I don't think the rest of the language would map well to the browser whose core DOM API is designed around objects, inheritance, and exceptions.
I wouldn't say Dart hasn't gone anywhere. Its gone from 81st place to 17th on tiobe in just 1 year. To me, that is going somewhere.
The big advantage of Dart over JS is the type system. Switching to Go would mean throwing that away.
PureScript and ClojureScript all have type systems better then the one in Dart. The simplest ways to get a type system is TypeScript. Not sure how I how it compares.
"Better" is subjective (and I certainly wouldn't consider any dynamic system to be better than dart's) - Dart hits a certain sweet spot IMO, being simpler than a typeclass-based approach but far more usable than Go or Java. TypeScript is pretty nice but gradual, which is its own set of tradeoffs.
Dart has other selling points than the type system, sure, but degrading it to Go-style types would be a serious loss.
It would be great to see what could be accomplished with a big-budget GopherJS.