simono

Dotty will inevitably implement the same features with the same fundamental issues. This is not about some old stuff we all regret having in Scala, this is about new low-quality proposals. When they get rubberstamped, they will end up in both Scala and Dotty.

Don't think so.

They won't be able to prevent the language from being run into the ground by SIP/SLIP/SPP committees.

Anyway, getting told that I'm not qualified to tell people that their new language extension ideas tick all the boxes of "bad ideas that we are regretting and deprecating since years" after I have more or less managed deprecations and removals for four major versions of Scala ... I guess they need to find someone else to do my job now.

But given past experience, the people who are eager to add more and more features are seldomly the people who clean up after themselves.

Most upcoming language proposals have extremely poor quality, ignore years of lessons learned, repeat many mistakes of the past, reinvent things that have been tried without success elsewhere and have no respect for design principles that made Scala great.

So glad that my name won't be associated with this.

> As an observer none of the powers that be took a liking to you calling them out

The best way to avoid being called out for saying completely different things in public and private is not saying different things in public and private.

If me politely asking for clarification about this sudden change of opinion is "underhanded behavior", or "renouncing from future interactions" means "let's find some flimsy pretext to contact your place of work to tell them what an evil person you are" then Scala might have some issues attracting and retaining contributors in the future.

Kotlin is a joke, but Scala's mismanagement and treatment of its contributors might be its undoing. Source: #1/#2 top active community contributor (depends on whether you count commits or locs in scala/scala) leaving Scala, because I'm tired of their shit.

I wonder how people come up with these pointless, overcomplicated tutorials...

Why do bloggers focus on lexing and parsing? These things should not take up 80% of the article about creating a programming language.

This fascination with "how" to build something, without considering "what" and "why", seems to be an issue that gets repeated time after time again.

The article isn't very good, even the link to the 'official' page is outdated.

Just use sbt-android and skip all the other nonsense.

Compilation is impressively fast, as the plugin uses the information from incremental compilation to skip ProGuarding completely for things that haven't changed.

Which issues did you experience?

I don't think the Scala-on-Android devs have any plans of giving up, they just took a wait-and-see approach until Google ships their new Jack/Jill stack: http://get-scala.org/2.12#scala-on-android

There is no sense of hurry as 2.11 won't go away and will have a long life.

In my experience it is.

The sbt-android plugin is really amazing. It makes compiling with ProGuard enabled as fast as Gradle without ProGuard, due to the plugins integration of incremental compilation with ProGuard.

Plus, there are quite a few built-in features and "add-on" plugins which enhance the experience further (sbt-android-protify, sbt-android-gradle).

A bunch of people built an "official" website around Scala-on-Android recently, scala-android.org. If you have any questions drop by in the Gitter channel: https://gitter.im/scala-android/sbt-android

I haven't announced anything and I haven't submitted this link to HN. I just added a comment to let people know that I might read and try to answer questions if they have any.

This submission's title at least reads "release notes" and not "2.12 released" like the submission yesterday, when people found the artifacts on Maven.

I'm the main author of this page (I took the "official" release notes and rewrote/extended them massively).

Feel free to ask questions!

(Please note that 2.12 hasn't been released yet.)

If I remember correctly, for 2.12 the compiler will generate additional forwarder methods, which mitigates the performance issues, but increases file size again.

It's still a lot smaller than 2.11, but for instance the standard library of 2.12.0-RC1 was 900kB smaller than 2.12.0.

Not officially announced/released yet, but here are (better) release notes: http://get-scala.org/2.12