HNHacker News
TopNewBestAskShowJobs

airless_cotton

22 karma · joined March 26, 2016

submissionscomments
airless_cotton··on Android Studio 2.0 Is Google’s New, Improved Development Suite
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).

airless_cotton··on Android Studio 2.0 Is Google’s New, Improved Development Suite
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's `android` tool anymore!

Maybe this is of use to you.

https://github.com/scala-android/sbt-android/commit/7b32e55f... https://github.com/scala-android/sbt-android/commit/53b855de...

airless_cotton··on Android Studio 2.0 Is Google’s New, Improved Development Suite
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."
airless_cotton··on Android Studio 2.0 Is Google’s New, Improved Development Suite
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 build without ProGuard.

That dev implemented and shipped Instant Run way before Google "invented" it, and it's still faster compared to Google's implementation.

airless_cotton··on Go 1.7 toolchain improvements
TIL that there are still people who believe that parsing has any impact on compilation speed.
airless_cotton··on An OCaml manifesto – Problems and what's needed for widespread adoption
I wonder why you feel the need to comment if you haven't understood the issue.
airless_cotton··on An OCaml manifesto – Problems and what's needed for widespread adoption
(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 instances.
Those two should be hard compiler errors, because they break data structures at runtime and make code behave incorrectly.

Sorry, orphan warnings are multiple magnitudes of escalation levels away from what should happen and are focused on something different (code hygiene vs. THIS-CODE-IS-WRONG-AND-BROKEN-AND-WILL-CORRUPT-SHIT-AT-RUNTIME-I-WILL-FAIL-TO-COMPILE-THIS).

airless_cotton··on Why you should come to LambdaConf anyway
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 of people and companies who tried to kill the conference and never sell them a ticket to a future conference again. (No bad blood, just helping them remember their big words.)

airless_cotton··on Var and val in Java?
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 a subclass" and "you can't reassign this value" as Java did with final, it clearly separates these concerns:

  class Foo {
          var qux = 1.23
          val bar = 42
    final var fiz = "fiz"
    final val wow = "wow"
  }
  
  (new Foo).qux = 2.34  //   valid
  (new Foo).bar = 23    // invalid
  (new Foo).fiz = "fuz" //   valid
  (new Foo).wow = "wew" // invalid

  class SubFoo extends Foo  {
    override var qux = 2.34  //   valid
    override val bar = 23    //   valid
    override var fiz = "fuz" // invalid
    override val wow = "wew" // invalid
  }