Never even heard of this until today.
replyI think they are doing a terrible job with their product packaging. Like others, I also gave up with Google models long ago due to difficulty in accessing and low limits.
My gut is that this is reflective of their fragmented internal product organization around AI.
Google has been like this forever.
replyExcellent engineering and awful product.
It's okay to say that Google's engineering is also poor. If they had good engineering, they'd study their users and lead to product improvements. It's really not either/or.
replyIt has been a while, but I used to read AOSP source code quite regularly, and always wondered where do all those engineers that pass the famous Google interviews land, because they certainly weren't writing the Java and C++ code in Android, given how it looked like, or the whole mess with NDK headers, and other stuff in the tooling.
replyAh, and the Eclipse/Android Studio stable releases, that usually have bugs as if they were still preview, release candidate ones.
What's clear to me: leetcode and quality code are not the same skillset.
replyUhg that’s my issue. I keep getting it mixed up with https://wave.google.com/
replyGo with the Flow, don’t ride the Wave.