4 ms·

Cross Compilation isnt unprecedented various lisps have been doing it for decades. There are many lisp solutions thats do it already. Including Clojure which sh

Cross Compilation isnt unprecedented various lisps have been doing it for decades. There are many lisp solutions thats do it already. Including Clojure which ships to Backend Frontend and Mobile Apps. Nothing new here.

adamnemecek 9y ago
Not talking about cross-compilation, I'm talking about having a industry-grade, production ready language that I can ship stuff in like yesterday. > various lisps have been doing it for decades There's an insanely long road from having a prototype of a language to having a production ready thing. There isn't a lisp where I could achieve the same experience.
- pankajdoharey 9y ago
  >I'm talking about having a industry-grade, production ready language. It isnt a mature enough language to be trusted so soon, no body has a sufficient enough industry grade experience with it. Especially with large code bases.
  - adamnemecek 9y ago
    > It isnt a mature enough language to be trusted so soon, I mean, Google adopted it as a first class citizen language on android which counts for something. > no body has a sufficient enough industry grade experience with it. Especially with large code bases. There aren't really any "new" features in Kotlin, as in features you haven't seen before. If you've been programming Java and know some Haskell/Ocaml or idk what else, you are good to go.
    - geodel 9y ago
      > I mean, Google adopted it as a first class citizen language on android which counts for something. Something but not much. It works on JVM, talk to all Java libs and tooling is taken care by Intellij. It is low or little effort from Google to support. Unlike other language fans who clamor for Android support from Google, here hard work is done by someone else. So Google support looks most like a co-branding deal.
      - adamnemecek 9y ago
        Not what we are arguing about. We are arguing about if Kotlin is mature or not, googles invovelement is irrelevant.

adamnemecek 9y ago

Not talking about cross-compilation, I'm talking about having a industry-grade, production ready language that I can ship stuff in like yesterday. > various lisps have been doing it for decades There's an insanely long road from having a prototype of a language to having a production ready thing. There isn't a lisp where I could achieve the same experience.

pankajdoharey 9y ago
>I'm talking about having a industry-grade, production ready language. It isnt a mature enough language to be trusted so soon, no body has a sufficient enough industry grade experience with it. Especially with large code bases.
- adamnemecek 9y ago
  > It isnt a mature enough language to be trusted so soon, I mean, Google adopted it as a first class citizen language on android which counts for something. > no body has a sufficient enough industry grade experience with it. Especially with large code bases. There aren't really any "new" features in Kotlin, as in features you haven't seen before. If you've been programming Java and know some Haskell/Ocaml or idk what else, you are good to go.
  - geodel 9y ago
    > I mean, Google adopted it as a first class citizen language on android which counts for something. Something but not much. It works on JVM, talk to all Java libs and tooling is taken care by Intellij. It is low or little effort from Google to support. Unlike other language fans who clamor for Android support from Google, here hard work is done by someone else. So Google support looks most like a co-branding deal.
    - adamnemecek 9y ago
      Not what we are arguing about. We are arguing about if Kotlin is mature or not, googles invovelement is irrelevant.