4 ms·

If it's slower than a webview, I strongly suspect you're holding it wrong. However "if you do it the naive/obvious way, it performs this badly" is not a good p

by mst 2y ago

If it's slower than a webview, I strongly suspect you're holding it wrong. However "if you do it the naive/obvious way, it performs this badly" is not a good property of a system and still probably explains why so many things are dog slow to get going. (I doubt I'd do any better than you did myself, mind, I'm pretty sure I have even less idea what I'm doing on android than you do) I'd be willing to bet the price of a pint that if either of us flailed around on iOS instead we'd probably end up with much better startup time even hardware-for-hardware because the easiest path for us to flail down is probably much saner than the equivalent on android. (insert rant about APIs needing to make sure the natural path that a newbie takes is also a path that produces -good- results even if they'll still need to git gud to achieve -excellent- results)

toast0 2y ago
> If it's slower than a webview, I strongly suspect you're holding it wrong. I sincerely hope you're right. But I was following the path as best I could, so I'm just not sure how it could have gone so wrong. I do 100% agree with your assessment of my flailing though. ;) It wasn't the only source of frustration (the weather API I was using looked good, but is actually crap, and their support blew me off when I pointed out data inconsistencies, so that's ugh). So it was easy to discard. Back to weather prediction by induction.
- refulgentis 2y ago
  I was an iOS dev for 7 years before G, then iOS app for Android watches for a year or two, then Android proper for...4 years? 100% cosign on the UI toolkit being.......ugh. There's a general saying internally at Google "$X is deprecated and $Y isn't ready yet", and I think that applies here, but I don't know Android UI as well as I'd like before damning it: I wrote Java + layouts for the one big UI feature I did, then was one of the first to do Kotlin, then moved to Flutter* from then on. In that vein: I cannot describe intensely enough how much I disliked Kotlin, and I get the vibe compose is not quite ready yet and isnt really moving the ball forward, as much as it's happy to be at general parity with SwiftUI. I really wish Flutter "won", it's such a beautiful and pleasant experience. Your job is a different job with hot reload. * Note: that was very unofficial, im almost certainly the only person who did on Android who was writing flutter, and it was because I ended up doing design system heavy work where having a web app to show designers things became paramount, no one was expecting much work on Android proper from me
- mst 2y ago
  Reminds me of an entry from my quotefile: < HellKat> the clock itself is set to UTC but it has a weather facility too - if you set the GPS coordinates < HellKat> temps right, weather however is wrong, comp says cloudy, looking outside says raining

by mst 2y ago

toast0 2y ago

> If it's slower than a webview, I strongly suspect you're holding it wrong. I sincerely hope you're right. But I was following the path as best I could, so I'm just not sure how it could have gone so wrong. I do 100% agree with your assessment of my flailing though. ;) It wasn't the only source of frustration (the weather API I was using looked good, but is actually crap, and their support blew me off when I pointed out data inconsistencies, so that's ugh). So it was easy to discard. Back to weather prediction by induction.

refulgentis 2y ago
I was an iOS dev for 7 years before G, then iOS app for Android watches for a year or two, then Android proper for...4 years? 100% cosign on the UI toolkit being.......ugh. There's a general saying internally at Google "$X is deprecated and $Y isn't ready yet", and I think that applies here, but I don't know Android UI as well as I'd like before damning it: I wrote Java + layouts for the one big UI feature I did, then was one of the first to do Kotlin, then moved to Flutter* from then on. In that vein: I cannot describe intensely enough how much I disliked Kotlin, and I get the vibe compose is not quite ready yet and isnt really moving the ball forward, as much as it's happy to be at general parity with SwiftUI. I really wish Flutter "won", it's such a beautiful and pleasant experience. Your job is a different job with hot reload. * Note: that was very unofficial, im almost certainly the only person who did on Android who was writing flutter, and it was because I ended up doing design system heavy work where having a web app to show designers things became paramount, no one was expecting much work on Android proper from me
mst 2y ago
Reminds me of an entry from my quotefile: < HellKat> the clock itself is set to UTC but it has a weather facility too - if you set the GPS coordinates < HellKat> temps right, weather however is wrong, comp says cloudy, looking outside says raining