3 ms·
A little bit off topic, but I have to vent somewhere... I don't know about Chrome, but if Android is their most high-quality thing, then at the very least they
by klibertp 4y ago
A little bit off topic, but I have to vent somewhere...
I don't know about Chrome, but if Android is their most high-quality thing, then at the very least they are also losing in developer experience. The churn in libraries and frameworks there is, from what I've seen, only second to Web frontend, and bugs in newer things are really embarrassing. "Ready for production" (they claim in the FAQ) Jetpack Compose is great when it works, but even the Android Studio-generated Compose template crashed the IDE several times, while manually setting it up crashed Kotlin compiler[1]. WorkManager and Room are important things that bugged out for me, too. And I'm at it for just 5 months - there's got to be way more dragons that I'm yet to see.
[1] https://issuetracker.google.com/issues/249653885 https://issuetracker.google.com/issues/249653885
- pohuing 4y agoStarting an empty watch face project has a ton of deprecated warnings as well. Not very reassuring...
- pas 4y agoI was mostly thinking about Android userspace/kernel/UX. The DX is of course tragic, and has been going down the drain since ... well, since the good old days of the first few years of Android Studio. But even back then it was a shitshow. When documentation wasn't completely useless then the APIs themselves were. (NDK is worth a dishonorable mention.) In-app payment APIs are also pretty meh - which directly make money for them! And yeah, there's Flutter, and now there's this new Jetpack/Compose whatever. But as is tradition it's nowhere near production ready. And when it becomes finally solid, they just abandon it. Angular went through the same cycle. I'm looking forward to their new React++ :D