1. 39
  1.  

  2. 22

    This reads a lot like “Kotlin is better than Java, hence better than any other language”

    1. 12

      I think it’s because the article has the unstated premise that you’re stuck with Java for one reason or another—because of Android, as in the author’s case, or because the codebase you’re paid to work on is already written in Java. By “whatever dumb language”, I get the feeling that he really does mean precisely Java here.

    2. 13

      This maybe isn’t necessarily the forum or what should prompt this, but I’m reminded that the language is generally one step in a process (code => debug => profile => release), and that being fixated on language “oneupsmanship” often loses the forest through the trees.

      1. 9

        Eh, but a given language has influences in all areas of that cycle. It’s also worth remembering that this was built by JetBrains, and I’d hope they’ve covered these points decently.

        Also, I think a central point of the article after the clickbait title is that Kotlin looks to be a far better JVM language than those that have come before, and that it makes Android dev more sane in various ways.

        1. 7

          The article content actually addresses a bit of that. Especially it coming from Jetbrains. The title is throwing a lot of people off.

        2. 5

          I can understand Kotlin might be a nice choice if you’re stuck in the misery which is Java. Having not used but read through a bunch of Kotlin documentation, as a language it will not be replacing Ocaml in my life.

          1. 5

            The problem of Kotlin is the JVM and the problem of the JVM is the lack of value types. It might come at some point (Yegge: “you’ve no doubt realized that by the time Java becomes a really good language, you’ll be dead”), but I would not bet on it. Kotlin cannot magically add value types (although they try) to the JVM.

            On the other hand, Kotlin wants to compile to native code via LLVM. I’m not sure about languages which target JVM, JavaScript, and assembly at the same time. I fear this will lead to sub-optimal experience for all of them.

            1. 4

              Arrogant title, but exceedingly humble article. Great read!

              1. 4

                I think the title is supposed to be funny and not antagonistic :)

              2. 3

                I’m excited about kotlin, which is indeed a gorgeous language, but I’m also a little sad clojure didn’t succeed as a better android language years ago. the main problems were toolchain friction and performance overhead, I think; kotlin has done an outstanding job of getting those both right from the outset.

                1. 3

                  You could also use F# with Xamarin, be essentially writing OCaml and actually have a good time.

                  1. 2

                    Hmm. Call me stupid but just what is a “DSL”?

                    1. 5

                      “Domain Specific Language”

                    2. 2

                      Why clickbait is better than whatever honest title you’re using?

                      Honestly, the article is good, but I am sick of click-bait and disappointed to see it on lobsters landing…

                      1. 5

                        Maybe it helps if you’re familiar with the author? I’m pretty familiar with Yegge’s writing, so as soon as I saw his domain on the entry I understood the title to be tongue-in-cheek

                      2. 2

                        This article title says “The author is immature and can’t make a good argument, so resorts to infantile insults instead”.

                        Not particularly motivated to read this.

                        Come on people, titles should be like dish names on a menu - They should invite, entreat and tempt - insulting the reader before they even start is just tawdry.

                        1. 6

                          The web domain itself says the article is likely to be a very good read. Steve Yegge doesn’t blog often, but I’ve enjoyed most of his stuff. Doesn’t excuse the clickbait title, but it easily signals why it might be worth looking past.

                          1. 2

                            Oh. I noticed the Kingdom of Nouns reference but didn’t notice it was actually the person who coined that.

                        2. 1

                          Spend entire article shitting on Java. Then lists reasons why he likes Kotlin. #1 is “It works like Java”