I dunno. I feel like what this article is about is how Google is perhaps detrimentally changing the developer preview for android and how it might affect the developers who use it to develope their apps. It doesn’t necessarily have to be detrimental but if your app works in one developer preview but not in the next or vice versa, it’s easier to pinpoint what changes were made between previews when they’re tied to a specific developer preview number and you can tell which features have changed or been newly implemented.
I agree with @Illecors@lemmy.cafe . The whole argument in the article is that unfamiliarity is scary. Despite the fact that all other Google products follow a similar model. Google have made it so that Canary is omnipresent and they can drop in and out features as they want for testing. The article writer is like, but at least the old way, we were sure. Even though there’s plenty of times things have come and gone for QPR’s and Developer Previews. It’s moaning for the sake of moaning and now saying very much. It’s actually embarrassing that the author got paid for such an article.
This should not be here. It’s a 121 word tweet, at best. A useless rambling of an excuse of an article.
I dunno. I feel like what this article is about is how Google is perhaps detrimentally changing the developer preview for android and how it might affect the developers who use it to develope their apps. It doesn’t necessarily have to be detrimental but if your app works in one developer preview but not in the next or vice versa, it’s easier to pinpoint what changes were made between previews when they’re tied to a specific developer preview number and you can tell which features have changed or been newly implemented.
I agree with @Illecors@lemmy.cafe . The whole argument in the article is that unfamiliarity is scary. Despite the fact that all other Google products follow a similar model. Google have made it so that Canary is omnipresent and they can drop in and out features as they want for testing. The article writer is like, but at least the old way, we were sure. Even though there’s plenty of times things have come and gone for QPR’s and Developer Previews. It’s moaning for the sake of moaning and now saying very much. It’s actually embarrassing that the author got paid for such an article.