Fair warning, you do lose access to some offline AI features like improved voice dictation and song recognition as well as Google Pay. I’m okay with the tradeoff personally but it is still a downside.
Fair warning, you do lose access to some offline AI features like improved voice dictation and song recognition as well as Google Pay. I’m okay with the tradeoff personally but it is still a downside.
continue
is useful as a loop analog to early return in a function context, which helps keep indentation/nested conditionals under control and in turn improves code readability.
I don’t think I’ve ever felt the urge to apply an alignment chart to monospace fonts of all things, but Xenon and Radon are basically lawful and chaotic evil respectively.
Nope, different product with almost the exact same name lol.
Nah, I did this once and didn’t notice until the call was placed because I was a little tipsy and engaged in conversation. IIRC it didn’t make any noise since my phone is always on vibrate, it just buzzed a bit and by the time I processed what was happening it was too late and I had to explain to the dispatcher that no, I was just fidgeting with my phone.
They can now be installed from the Play Store and both apps work without issue.
This article seems to be outdated as both apps are now visible in the Play Store and I had no problems downloading and running them. A comment suggests that it may be due to the previous minimum SDK target for the apps being too low. I’d be willing to chalk this up to being more innocuous than active malice on Google’s part.
I mean, technically there’s nothing preventing that, but in practice it’s a fairly uncommon mistake to make and it’s immediately obvious that there’s an issue the first time that path is taken. If something like that makes it to production, it clearly points to an issue with test coverage rather than code paradigm.