I’m not saying this is JB’s plan, I rather advocate for JB to keep a high level of Eclipse support to help Kotlin adoption.

I agree, @dh44t , but stranger things have happened.

what you say, it's surely a possibility, @strindberg, althought I am pretty sure it's a very low one

I’m not trying to be a pain here. It’s just that I am a recent Kotlin convert, trying to convince my group to adopt Kotlin. One of the questions I get has been “Will we be forced to use IntelliJ?"

I am in the same position as you

that argument makes zero sense. 1. kotlin support is open source. 2. if jetbrains could drop the free kotlin plugin from idea they could also drop the eclipse plugin.

and everybody is free to work on the eclipse plugin anytime

Netbeans support is quite important also for me, because I'd like to introduce Kotlin in our core module. But for the moment I have a lot of external tools that can be written (and I am writing them) completely in Kotlin and used from Java side without problems.

You’re right, @christophsturm . Being open source, someone can always pick up the baton if needed. Perhaps that scenario was too far fetched. But my point is still that if Kotlin is perceived as requiring a JetBrains IDE, it will hurt Kotlin adoption. I’m not expecting JB to be altruistic and give this tool to the world without a realistic chance of profiting. I’m rather interested in further interest in Kotlin, in my group as well as in general.

But it doesn't require a JetBrains IDE, right? Or are you saying the Eclipse plugin is so buggy/useless that it may as well not exist?

it doesn’t require IDEA but IDEA CE is free so...

^ and much better than Eclipse (IMO of course)

I am saying that if the Eclipse plugin is four months behind, and does not support the latest version of Kotlin, it’ makes is more difficult for me to point to it and tell my Eclipse-loving colleagues that switching to Kotlin is a great idea.

it does support the last version. The word "support" is another problem thou

I am surprised that it’s so difficult getting the point across: I too prefer IntelliJ over Eclipse, and I would be very reluctant to adopt a new language that forced me to use Eclipse, if it was the other way around.

but doesnt support spring for example 😉

I think that supporting multiple ides is a complex and time consuming task

android in the same way, Android dropped support for Eclipse. So they will probably continue to work on Eclipse and Netbeans plugin but as said before I find it not surprising that they are focusing on IntelliJ

and I think Intellij is so great that a team that need to migrate to Kotlin should first migrate to Intellij 😛

I do get your point

The way Ceylon is tied to Eclipse was offputting for me for instance.

However, there is a plugin. The language hasn't changed in the past 4 months, so beyond new features, what are you expecting to be added?

but now they have an IntelliJ plugin

I guess it depends how you define support - continual improvement?

yeah, when I was first checking it out they didn't though, I think

Hey I have a question of style. Do you guys use

.add()

or

+=

on collections?

(also: is there any “official” code style doc anywhere for such questions?)

i’ve been using

+=

@mikehearn I also suffer by unbalanced work on different IDE, esp. this Eclipse-related bug is a show-stopper for me... https://youtrack.jetbrains.com/issue/KT-10361

I work with Bndtools plugin and having classfiles from Kotlin on the disk is crucial for any serious development