Not sure how everybody else feels about it, but I find that optional typing is the enemy of readable code.
Iodine: A full superset of Java with enhancements
31–40 of 69 posts
Re: Iodine: A full superset of Java with enhancements
#32I don't get it: there is already a widely accepted 'better' Java called Kotlin, that features much more than this: way better integration with IDEs, way better integration with existing Java codebases, better everything... Yet somehow we should start using NEW IDE with NEW language supported by completely unknown company with zero guarantees about its support. I just don't get it.
And Scala, and Groovy...
Furthermore iodine is already the name of a popular IP-over-DNS tool.
Re: Iodine: A full superset of Java with enhancements
#33Not sure how everybody else feels about it, but I find that optional typing is the enemy of readable code.
It doesn't look like this has optional typing (like Dart or Groovy) but local type inference (like Kotlin or C++).
Re: Iodine: A full superset of Java with enhancements
#34Someone should just do C# for Java and be done with it...
Yeah it's called Kotlin, better than C# IMO.
Re: Iodine: A full superset of Java with enhancements
#35What problem does Iodine fix[0]?
Here is my guess at an answer.
Iodine: our Java implementation should include features from newer languages
Re: Iodine: A full superset of Java with enhancements
#36Re: Iodine: A full superset of Java with enhancements
#37Earlier quoted context omitted.
Android Studio is based on Intellij.
Every developer with Android experience knows that, and both require more resources than either Netbeans or Eclipse, but whatever Google makes to their fork of Intellij, makes Android Studio even worse.
The android dev tools have never been that great, and I feel they’re even worse with the new Gradle build system (although yay, Maven dependcies without needing to pull in Ivy?)
I use IntelliJ daily without issues, literally the only difference between my work and that of a Android Studio user is the Android plugin and the different build system.
Re: Iodine: A full superset of Java with enhancements
#38I don't get it: there is already a widely accepted 'better' Java called Kotlin, that features much more than this: way better integration with IDEs, way better integration with existing Java codebases, better everything... Yet somehow we should start using NEW IDE with NEW language supported by completely unknown company with zero guarantees about its support. I just don't get it.
The difference is that it's a superset, whereas Kotlin is a different language with Java interop, that's designed to be familiar to Java programmers.
To use a JavaScript analogy, Kotlin is CoffeScript, and Iodine is Typescript.
Re: Iodine: A full superset of Java with enhancements
#39Someone should just do C# for Java and be done with it...
Yeah it's called Kotlin, better than C# IMO.
Kotlin is cool but it's not C#. The project that's most "C# for the JVM" is called Stab and it's widely rumored that it was (as its an anonymous project) a precursor to Kotlin on the side.
Re: Iodine: A full superset of Java with enhancements
#40> Let's face it: Nobody loves working in Android Studio, Eclipse, or NetBeans – the IDEs are bloated, clunky and unintuitive. Uh... I don't agree for IntelliJ/Android Studio, and I'm sure some people love to work with NetBeans and Eclipse.
I love Eclipse for working in Java, and I love IntelliJ for working in Kotlin. My impression is that people who don't like IDEs haven't put the effort into figuring out how to use them effectively -- modern IDEs have incredible power to increase productivity, but you have to learn how, and you have to make some accommodations in how you work. I say this from experience: I started my career coding C/C++ in Emacs and I…
My general experience is that Java needs an IDE because the language forces a bunch of boilerplate and a file/directory structure that is very difficult to navigate without a bunch of tooling. However, in other languages, the gap between the IDE experience and the well-configured vim/emacs experience is much narrower.