Kotlin 1.0 Released
Qbertino writes: Kotlin, one of the challengers to Java's VM, has been released in version 1. Kotlin is object-oriented, statically typed and comes with professional IDE support by Jetbrains — which is no big surprise, since it's the Jetbrains employees who developed the programming language that saw the light of day four years ago. Kotlin is already in real-world use and development will be moving into fleshing out the Kotlin feature set without breaking backwards compatibility. These features include planned support for JavaScript — which sounds interesting considering JS has gained quite some traction recently. Kotlin is FOSS and is released under the Apache license.
Provide an actual working installer, instead of that Sun invented piece of misnamed, misplaced piece of camel dung instlaler. First you have the magicalliy renumbering component versions, then the "you have to formally sign a user agreement" to instlal it, then for RHEL and CentOS and Fedora and SuSE users you get misnamed "rpm.bin" piece of sticky doggy mess that violates the File System Hierarchy and whose RPM package name does not match the name of the RPM file.
There are reasons some of us gave up on using anything from Sun, and it's sad to see Oracle continued the same stupid practices. If these Java variant exert the slightest care in packaging, they can pick up a few clients right there.
Which is it? The summary makes it sound like Kotlin has its own VM (JVM compatible I'd assume) to compete with Oracle's JVM. The web page makes it sound like Kotlin is just a language that compiles to the JVM's bytecode. Which is it? Or is it a both?
Kotlin is yet another language to be run in the JVM. It is not a competitor to the JVM as the description suggests.
So of course I had not read the link. It is not a VM as TFS claims, but just a language within the Java VM, therefore an alternative to Groovy, JRuby, Scala. In particular it is different because it is statically typed but more compressed/expressive.
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
All the new JVM based languages that are popping up are just syntactic sugar on top of Java. The real concepts can't be shaken, as the JVM is pretty much limited in what it can do and what it can't.
Telling from the examples, Kotlin seems to be a good example: Yet another poor copy of Java with some "obsolete" things like the semicolon removed (why is there so much hate for it?), and you write "fun" instead of "function". So what. I don't think this makes me more productive than Java. Its just for all the people who keep preaching "java is shit" because they've heard it somewhere and now they want to use a "much better" language.
If Kotlin suits, Java is fine for the job as well, and most likely its even better.
Jython is a non-starter because it is stuck on Python 2.5 compatibility.
JRuby, Scala and Clojure are still growing.
Just because you are ignorant of them it doesn't mean they are dead.
You want to know what's stupid? If you go to the main web page the only description of the code you get is a sample "Hello, World" application, and the link that claimed to lead me to more examples instead lead to an advertisement for a book on the language.
If you won't let me look at it... Why do you expect me to buy a pig in a poke.
I think we've pushed this "anyone can grow up to be president" thing too far.
If c programmers needed that level of support, they'd be told to go back to school and really learn the language.
Code completion is rather useful for libraries. It has obviously nothing to do with "language".
And I rather have my method calls autocompleted, especially when I also autocomplete arguments, than having the compiler give me 25 errors per file I worked on the last hour because I have a typo every where.
There are plenty of reasons why people use auto completion ... "not knowing the language" is very likely the least one.
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.