Hi people, we have PR for migrating to K2. The question left is K2 IDE plugin which is in alpha. I a...

# k2-adopters

[Eugen Martynov]

Hi people, we have PR for migrating to K2. The question left is K2 IDE plugin which is in alpha. I assume we can continue to use Kotlin 1.x plugin and we should probably get some compiler warnings for smart casting things. Or K2 plugin is already good enough in Alpha status? If you migrated, can you share your IDE strategy and if you noticed something blocking or annoying?

[Javier]

K2 compiler plugin status is about breaking changes in APIs. Probably the same status K1 had before being relegated by K2

[Eugen Martynov]

Javier, not sure I understood the comment

[Javier]

What I mean is they can break any API when they want, but I think it was the same for K1.

[Alejandro Serrano.Mena]

personally, I keep using the regular IDE plug-in even with 2.0 as my compiler version, and everything seems to work fine

note that no language features are going to be added until 2.1, so even though both K1 and K2 may give slightly different errors, at the end of the day they target the same language

[Javier]

Oh @Eugen Martynov I misunderstood you and I was thinking you were talking about k1 vs k2, no about IDE plugins

[Marco Pennekamp [JetBrains]]

I work in the K2 IDE team, so naturally I’ve been using the K2 IDE plugin for well over a year. For me personally, it is working very well. I prefer it over the K1 plugin as K2's performance is better & less erratic.

It depends on the use case/project of course whether switching right now would be a good idea. But it’s very easy to switch back and forth (a checkbox in the Kotlin language settings + restarting IntelliJ), so I’d suggest spending a few hours with it.

If you decide to try it out and encounter any blockers, the best thing to do is to let us know on YouTrack by creating an issue or voting for an existing issue.

[Eugen Martynov]

Thanks. We will avoid K2 right now, and we are waiting for the beta release. The main concern is that we will start writing K2 code that will not be well highlighted by K1 by other team members. We have quite a big team, and few people like walking on a bleeding edge.