Just double checking, <VERSIONING.md> sounds like it's saying that we can use a version of Google's ...

# compose-desktop

[eygraber]

Just double checking, VERSIONING.md sounds like it's saying that we can use a version of Google's compose compiler through the kotlinCompilerPlugin property. Is that accurate?

e.g. if I set that property to androidx.compose.compiler:compiler:1.4.0-alpha02 would I be able to update Kotlin 1.7.21 in my jetbrains compose project?

[jw]

As long as you're not using web, it should be fine (we find out later web is also fine on 1.4.0)

[jw]

Native, JVM, and Android totally safe

[eygraber]

Thanks, I'll quote you on the totally safe thing 🧌

[jw]

A JB dev said that they'd like to move away from using their compiler and use the Google one directly. Although with the recent web debacle and how glacial Google is to land and release fixes they perhaps shouldn't be too quick...

[eygraber]

Ah I vaguely remember this. They've been maintaining their own compiler because until recently Google only supported Android? And they can't go off of it completely because Google still doesn't support JS?

[jw]

JB landed the native and JS support in Google's a year or more ago.

[jw]

The problem is that when a fix needs to get made it takes Google forever to release

[eygraber]

Cuz they're a big company 👀

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1664463802854389?thread_ts=1664463601.592469&amp;cid=CJLTWPH7S

[jw]

Yeah that's 100% bullshit. KSP releases same day Kotlin drops. It's pure technical debt and self-imposed overhead.

[eygraber]

I forgot my 🧌

[eygraber]

So there's support for JS in Google's compose compiler, but they haven't provided a release with that yet?

[jw]

It's in every release

[jw]

For like 18 months now

[eygraber]

Native, JVM, and Android totally safe

So it could be used just not necessarily safe?

[jw]

For JS? It was safe until Kotlin 1.7.20 broke something it relied on. JB releases a hot fix to the compiler while Kotlin 1.7.21 was cooking.

[jw]

I believe I saw the fix get upstreamed so the latest alphas or whatever versions is the absolute latest probably also has it now.

[eygraber]

I was just quoting the message you sent earlier, assuming you meant that JS was not safe.

Is this the bug you were talking about?

[jw]

That is the upstreaming of the fix, yes.

[eygraber]

So I could "reliably/safely" use Google's compiler with a JB project for Native, JVM, Android, and JS, but not Compose for Web (the DOM one)?

[jw]

I'll do you one better: Every version is safe for JS except for 1.3.2 specifically. 1.3.1 and older is safe (with their appropriate Kotlin versions). 1.4.0-alpha01 and newer is safe (with their appropriate Kotlin versions). It's just 1.3.2, and that's why JB released a 1.3.2.1 version which contained that fix.

[jw]

You can see that 1.4.0-alpha01 contains the fix in the release log: https://developer.android.com/jetpack/androidx/releases/compose-compiler#1.4.0-alpha01

[eygraber]

Works for me 😄

Thanks!

[Arkadii Ivanov]

I'm not sure, but in the docs it's said:

However, keep in mind that this compiler version isn't tested with Compose Multiplatform, so stability isn't guaranteed.