![]() ![]() There is no official public word from Jetbrains other than some comments in some KEEPs that are often several years old.ĭisclaimer: I am working on a project that uses multiplatform Kotlin JVM/JS with extensive use of coroutines, kotlinx-serialization and kotlinx-html libraries. Those 2 KEEPs that linked to? We don’t even know whether Jetbrains wants to implement them, let alone what the time frame for them is. But we don’t even know which KEEPs will be accepted. I don’t necessarily need to know when a feature will be available. See Jake Wharton’s Kotlinconf 19 talk for a comprehensive summary of new Java features in the next 3 years.įrom jetbrains there is no information whatsoever. Those Java features are very exciting to talk about. They have outlined language features for the next 3-4 years. It might not be enough to keep people interested, certainly not enough for the classical JVM Backend Developer.Ĭompare it with Oracle’s information policy. Also I understand the importance of native and multiplatform, but they are quite niche currently. I understand that there is lots of progress under the hood in improving and fixing underlying systems. ![]() Guess what, it feels like there was no progress at all. I wrote a similar post more than a year ago shortly after the Kotlinconf 2018. Who knows maybe they have some other great feature idea that we don’t know about.Īpart from all that there has been done a lot of work on multiplatform and native, mainly on the library side I think, but I mostly use kotlin jvm so I’m not entierly sure the exact focus there. My guess is that after the compiler rewrite is finished JetBrains will work on finishing those features as well as maybe adding pattern matching or taking a look at keep 87 (compile time extension interfaces) or keep 176 (compound extensions), but this is just a guess. Both still experimental but this shows that there is still ongoing work on new features. ![]() My guess is that this is a necessary step before adding more complex features and will also probably speed up development since the different platforms are more streamlined.Īlso there are 2 big features since 1.3 that you missed in your summary. They’ve been working on a complete rewrite of the type inference and are working on a complete compiler rewrite to increase compile speed and alow for more flexibility in the future. 1.4 on the other hand is mostly focused on small things and compiler improvements as well as multiplatform. It’s true that there haven’t been any flashy features since coroutines, but promoting them to stable was a big step IMO, since for many companies that the earliest point they become viable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |