airless_cotton

4 ms·

1.
by airless_cotton 10y ago
Did you give https://github.com/scala-android/sbt-android-protify a try? It exists longer than Google's "Instant Run", is faster and works without flaws (in my experience).
2.
by airless_cotton 10y ago
As far as I know, sbt-android just recently got even more support/features for NDK (on top of the existing support): The plugin can now manage and auto-install SDKs, tools, support repos and NDKs, so no messing around with Google'
3.
by airless_cotton 10y ago
Yeah, it just shows that Google clearly sees app developers as sharecroppers. "Don't like our terrible software quality and negligence? GTFO, there are hundred other desperate people writing the same app."
4.
by airless_cotton 10y ago
Migrating to sbt-android has been a revelation coming from Gradle. It's bizarre that a one-man-team beats the mighty Google in pretty much everything. The build is so freaking fast that it runs ProGuard by default – and beats a Gradle
5.
by airless_cotton 10y ago
TIL that there are still people who believe that parsing has any impact on compilation speed.
6.
by airless_cotton 10y ago
I wonder why you feel the need to comment if you haven't understood the issue.
7.
by airless_cotton 10y ago
(Sorry, forgot password to my old account.) Orphan warnings tell you that you defined an instance in the wrong place. Things you don't receive warnings for: - Defining the same instance twice. - Having code which uses both in
8.
by airless_cotton 11y ago
I really hope that the mob is proud of its actions when the conference is canceled. "Hey, everybody is worse off now, but at least me made our point!" If the conference isn't canceled, I really hope the organizers make a list
9.
by airless_cotton 11y ago
One aspect that the author mentions only in passing–but is interesting to look at in more detail–is to understand how Scala has solved this in a very consistent and satisfying fashion: Instead of mixing "you can't override this in