2

Why the fuck would Google promote Jetpack Compose as a stable toolset when it doesn't even support a basic feature such as a scrollbar.
A. Fucking. Scrollbar.
LazyColumn can't even come close to being as powerful as Recyclerview.

Here's an idea, before launching something and touting it as something usable, and encouraging people to drop the old, battle tested tool for the new shiny one, how about you make sure the new doesn't lack features present in the old one?
Seems logical, right?

Methinks somebody was just looking for a promotion because, clearly, Jetpack Compose is a half-baked product.
Now, developers will have to suffer because project managers will read about the new framework and ask devs to use it, then wonder why the app is suffering.

Comments
  • 1
    Personally I think jetpack compose is better.
    If you know jetpack compose you can build on any platform, even desktop.
    I prefer lazy column then trying to write an adapter for every recycle view.
    Compose is still new in the market so there might be some inconvenience. But there always a way to work around to fix things https://github.com/nanihadesuka/... https://gist.github.com/mxalbert199...
    I am not an advocate for compose, but I will choose compose any day
  • 1
    It needs time to mature. You can’t just release something that replaces the whole Android UI SDK and be completely done. This shit takes time and feedback from users.

    It’s meant to be used together with the old system. Fall back to the old stuff whenever you hit a roadblock.
Add Comment