ScalaDays 2012 – Odersky's Keynote: Where Scala is Going
skillsmatter.com13 pointsby soc883 comments
-- Democratic People's Republic of Korea
Smoking isn't just a profession, it's an everyday skill
that everyone should learn, regardless of how badly.
A cigarette is a great enabler for this - and I endorse
this direction completely.
-- Your friendly tobacco association.
"Beating"? The JVM is configured to take as much available memory it thinks is necessary to speed up execution. Go lacks pretty much any runtime optimization and therefore doesn't do that.
> Scala is a statically typed language but it must do runtime type reflection to implement some of its features on top of the JVM. That comes at a cost (and in fact we decided not to implement Go on the JVM for this exact reason).
That's just non-sense. You take some (actually discouraged) corner cases of a completely different language to arrive at the decision to roll your own runtime (something the team seems to be completely unqualified for, judging the current state of the GC in Go?).
> My observation of similar Go programs is that these kinds of problems don't really come up.
Yes, because no one actually uses Go for anything where GC or latency would actually matter. Not even the garbage collection is working properly today. Please, show me some Go application server running with 128 GB heap doing something useful.
I don't think Go (or Dart) will have any mid- or long-term impact. The "OMG, we're at Google, we're so brilliant, let's design a language for all those stupid non-Google losers out there" approach to language design isn't working out so well, it seems.
Not even mentioning how seriously they messed up their "error" checking design. Confusing product with sum types ... god, you can't make that up.