I'm making a prediction that Kotlin 1.4 will be re...
# random
d
I'm making a prediction that Kotlin 1.4 will be released on 17th of March 2020. I'm leaving this here as proof. 🙂
👀 1
🤔 4
r
Interesting, I'm curious to know what you have based this prediction on.
d
I pretty much extrapolated based on previous releases, how long it'll take to implement what I think will be released in 1.4 and added some padding in some places. I just did some napkin maths. Not hoping to be correct (earlier is better lol) but just curious as to how close I'll be to the actual release.
r
Alright, cool. Too bad slack doesn't let you add a reminder that far out.
h
Isn't there usually a release very shortly after the kotlinconf? (Or is 3 months the usual delay? It might just be me not realizing how much time actually flies inbetween there ...)
🚫 1
d
In a podcast/interview, Andrey Breslav says not to expect 1.4 for the next KotlinConf. So I've accounted for that.
h
Oh, So this is quite scientific after all, then. Let's all just wait for St.Paddy's then.
n
starred to find this next year.. or on the 1.4 release
f
What do you think will be implemented in Kotlin 1.4? Originally I thought Keep87 but now I don’t think the priority on that is too high.
d
IR and the multi-platform story that comes with it. Inline classes stabilisation. All the kotlinx io stuff we've been waiting for (Although this isn't strictly related to 1.4).
t
imho kotlin-native goes stable
m
Version every two months - 1.3.60 in October, 1.3.70 in December, 1.3.80 in February, 1.3.90 in March... overflow, 1.4.0 in May.
t
why not 1.3.100? 😏
d
I was assuming 1.3.60 will be the last one but now I think 1.3.70 might be last. Since 1.2.70 was the last one for 1.2 (Although 1.1.60 was the last one for 1.1). Predicting the future is tricky business. In the end, it's a slightly educated guess.
f
If .60 was the last for 1.1, and .70 was the last for 1.2, then obviously .80 will be the last for 1.3. Predicting the future is not that hard.
d
That was my first instinct but there are no signs of a dev release of 1.3.80 and target versions in YouTrack stop at 1.3.70 then continue at 1.4. 🤷🏼
n
so .90 for 1.4 and what for 1.6 ? .100 ? that will make sorting versions a pain
r
No, that would be for 1.5. 1.6 would be .110. Personally, I can't wait for version 1.95.1000.
f
Kotlin 2 is just Scala
😠 3
p
What is your prediction on when is a usable Kotlin IDE going to be released?
r
Is IDEA not usable?
p
It's not.
Not if you accept 2 minute delay on code-highlighting and other huge performance issues caused by Kotlin compiler being too complicated.
<https://youtrack.jetbrains.com/issue/KT-32158>
<https://youtrack.jetbrains.com/issue/IDEA-222885>
<https://youtrack.jetbrains.com/issue/KT-32437>
<https://youtrack.jetbrains.com/issue/KT-30726>
Brought to you by "language designed with tooling in mind".
r
Fair point. I'm missing the nuance of your last comment. Did you mean to insinuate that Kotlin is not living up to the claim of being "designed with tooling in mind", or that designing a language with tooling in mind is itself a bad idea?
p
Good question. I am honestly not well versed in writing IDEs so I am not sure what the problem is. Kotlin seems to have a lot of bells and whistles that make the IDE experience even "smarter" but maybe it causes the performance to suffer. Maybe there is just too much inference, too many hints for the IDE to handle in timely fashion? In any case, the bottom line is that I love the language and I am devastated that I have to start converting parts of our project back to Java solely because of the IDE performance.
r
Indeed. Thanks for sharing. Personally I'm hoping the usage of IDEA improves instead of getting a whole new IDE.
j
converting your project back to java because of IDE performance of 2019.2 is an incredibly melodramatic approach. why not: 1) use a version < 2019.2; or 2) try 2019.3 EAP, which reportedly fixes the issue you're having
f
The IDEA version has nothing to do with kotlin editor performance
If it were up to me, I would put improving the performance at the top priority, with nothing else coming close
Actually, he is referring to problems that also exist in Java... I haven’t had any performance problems there
d
@Dominaezzz 1 month to go 😄
d
Ha! Yeah. (I didn't include
1.3.70
in my calculations. 😅 )
⏲️ 2