A modern programming language that makes developers happier.

kotlinlang

Looks like lots of things were removed from the roadmap....

What I don't understand: why put resources into eg. wasm when eg. Javascript support is still not "finished" and multiplatform has lots of bugs? :disappointed:

We’ve removed the “Postponed” column from the page. The reason for it was that we didn’t clearly understand what to put there. If we put everything that is postponed, it will be hundreds of issues, not very informative. If we put just some tasks, it raises many questions from people interested in other tickets.

So we decided to use the roadmap only to show items that we plan to work on in the upcoming six months.

However, the previously postponed tickets are still available in YouTrack, and you can watch them for updates.

&gt; why put resources into eg. wasm when eg. Javascript support is still not “finished” and multiplatform has lots of bugs?
Unfortunately, it’s not possible just to through more people at some problem and expect it to be solved faster. There are two primary reasons for it:
• <https://en.wikipedia.org/wiki/Brooks%27s_law|Brooks’s law> is inevitable.
• Different projects require people with different background and skillset. Our team has a very diverse set of backgrounds, and we should count for their strengths when defining priorities. Tooling developer won’t be very effective in the compiler-related work, and vise versa.
That’s why we aim at focusing the biggest part of our team on the ongoing activities that should be finished (K2 compiler, K2 IDE plugin, Multiplatform, JS IR). And ~5-10% of the team works on “experimental” projects, that should help Kotlin grow in the distant future.

<@ULR20LXNJ>, thanks for the answer, I understand it, and please don't get me wrong because I'm a long-time Kotlin supporter and "advocator".

But I see a big problem with the Kotlin ecosystem, and this is why it is very hard to recommend Kotlin for colleagues and companies lately: it feels like everything is experimental, alpha, beta or obsolete, and there are many-many unfixed bugs in all components. The amount of KT bugs is frightening - and even I report multiple bugs per day during using the IDE.
I love Kotlin and you/Jetbrains do a great job at developing it but maybe instead of always adding new features the focus should be stabilizing the current feature set. In a more conservative project there should be a "feature freeze" and focusing to make Kotlin more robust and fixing at least some of the bugs.
:(

I see your point Egor, but that does make this less of a "roadmap" and more of a parking lot. We can now see what is actively being worked on, but we no longer have any indication of what becomes a priority after your current tasks are finished.

&gt;  it feels like everything is experimental, alpha, beta or obsolete
Yeah, this sort of applies to other JB products as well. I assume that's their unwritten policy that allows them to be feature rich at the expense of stability. And, since I currently don't have any serious, real-time response business applications, this is fine by me.