I don't really use it a lot for programming. Whenever I'm writing some technical document and I find myself churning out some awkward sounding sentences (which happens a lot), I use ChatGPT to get some suggestions. I also find that ChatGPT gives better translations than Google Translate.
Not exactly a fan of Play Store policies, but for this situation, I'd say that Google gave ample time for developers to migrate to API 33, and all behavioral changes and API deprecations are documented (however annoying it is).
I get the author's sentiment. But speaking as an Android developer, we are forced to use newer APIs due to the following:
1. Deprecation - Google is notorious for deprecating APIs (it's a meme among Android devs) and we as developers are forced to move to using newer APIs
2. Google Play policies - From Google: "New apps must target Android 12 (API level 31) or higher; except for Wear OS apps, which must target Android 11 (API level 30) or higher."
3. Some APIs such as Jetpack Compose require a certain minimum SDK version (API 21). Therefore, if you want to use new APIs, you are forced to stop supporting old devices.
We wish we could continue supporting old devices but it's mostly out of app developers' hands.
I just wanted to correct a little bit of misunderstanding here about how target SDK works (and min SDK).
Having a target SDK e.g. at Android 12 doesn't prevent you from supporting versions of Android before 12, it prevents you from fully supporting Android devices newer* than Android 12.
The target SDK defines what is the minimum feature set that you have access to (and sometimes what you're required to implement). If you target API level 31, you can add all of the latest features (e.g. improvements around network usage to save energy that wasn't present in older SDK versions).
You, as a developer, decide on your "min SDK", which is the lowest level of Android that you're willing to accept. That is determined by how much you're willing to work around missing or buggy features in old SDK versions, something with is really helped out by using AndroidX (née Support Library), which is a shim you install that provides compatible implementations of newer features when your APK is installed on older phones (similar to polyfill on web).
* During the beta of a new target SDK, old phones won't run an app targeting it, this is to prevent people from building and shipping apps against a beta SDK.
that EAM had a weird number of repeated characters in it, more than I'd expect by chance if my ears aren't deceiving me. I thought they used a one-time pad, don't they?
Count me in. For me, it looks clean, and have no problems differentiating tabs. It's odd that people have a fit over this--not saying that people aren't allowed to dislike the changes but the negative reaction just seems over the top.
4chan was always kind of the "home" of Pepe memes, so it was kind of natural that the racists, incels, and other "alt-right" denizens of 4chan made (and still make) extensive use of Pepe and consider it "their own" to some extent. But the whole thing about specifically making Pepe into an alt-right symbol was just some shit they stirred up to "troll" the media. It worked, and the stigma stuck.
A lot of Pepe memes also ended up becoming Twitch emotes through BetterTwitchTV and FrankerFaceZ. And a lot of those emotes found their way into Discord chatrooms. In Discord, you can usually tell whether someone is an alt-right person or not by what Pepe emotes they use.
