IssueTracker

this would be nice but given Compose and all other priorities, we are not planning to make any big investments in data binding (support KSP is a very big task).

Makes sense. And is there any way to trigger data binding without kapt plugin, assuming there are no custom binding adapters in given module?

unfortunately no. data binding still needs to be able to read your code and annotation processing is the only API that allows us to do it :(

It's a very disappointing decision for many projects who heavily depend on data binding, which will never be able to get rid of all bindings code and especially rewrite all UI to Compose.

It means that bindings are essentially deprecated

It does not mean data binding is deprecated unless KAPT is deprecated (if that happens, we would need to support KSP).Unfortunately, moving data binding to KSP is a large order so it makes more sense to keep focusing on KAPT than rewrite data binding.

We might re-consider this in the future based on KSP becoming stable, Compose adoption and KAPT stability but it is very unlikely to happen.

KSP is now stable stage.
https://android-developers.googleblog.com/2021/09/accelerated-kotlin-build-times-with.html

Can google reconsider to adapt KSP on databinding compiler?

Unfortunately this is still a NO for 2022 planning due to reasons mentioned in #2.

kapt seems no longer adding new feature

kapt is in maintenance mode. We are keeping it up-to-date with recent Kotlin and Java releases but have no plans to implement new features. Please use the Kotlin Symbol Processing API (KSP) for annotation processing. See the list of libraries supported by KSP.

https://kotlinlang.org/docs/kapt.html

So this mean databinding will also deprecated or will be support KSP?

We don't plan to support KSP nor recommend data binding usage at this stage since compose is our recommended UI solution.

I have been waited this answer in several years.

Because it is an important basis to convince co-workers and for determining the technology stack of an app.

Databinding is in maintenance mode as well.

We don't plan to support KSP nor recommend data binding usage at this stage since compose is our recommended UI solution.

A bit of a tangent here, but what about ViewBinding? Will that one stay going strong or will it fade along with DataBinding?

Kotlin K2 compiler doesn't support kapt anymore, which means the data-binding library can be dead soon.

https://github.com/JetBrains/kotlin/blob/master/plugins/kapt3/kapt3-compiler/src/org/jetbrains/kotlin/kapt3/Kapt3Plugin.kt#L71-L76

Here is the tracking bug on YouTrack: https://youtrack.jetbrains.com/issue/KT-51982/K2-Support-Kapt

#14 Kapt will be supported on K2, there are no plans to stop supporting it in Kotlin