News for hackers. Stuff that matters.
Re:Brad Fitzpatrick on the future of Go by kingmanaz on Tuesday October 14, 2014 @11:22AM (#8453807)
Regarding the article's mention of GopherJS: The Google Dart project should adopt Go as its language and reboot. Dart hasn't gone anywhere. GopherJS is a great low-budget transpiler and its source could be incorporated into a Go-based Dart.

It would be great to see what could be accomplished with a big-budget GopherJS.

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.
Re:Brad Fitzpatrick on the future of Go by autechr3 on Tuesday October 14, 2014 @01:10PM (#8454454)
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.
Re:Brad Fitzpatrick on the future of Go by lmm on Tuesday October 14, 2014 @11:28AM (#8453834)
The big advantage of Dart over JS is the type system. Switching to Go would mean throwing that away.
Re:Brad Fitzpatrick on the future of Go by nickik on Tuesday October 14, 2014 @01:28PM (#8454568)
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.
Re:Brad Fitzpatrick on the future of Go by lmm on Tuesday October 14, 2014 @02:27PM (#8454910)
"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.