Multilayer recording sounds like it would require read-rewrite similar to how SMR works. Still perhaps we’d be okay with that for the dramatic capacity increase.

Why shouldn’t they do “r/Android V2” posts? Is [email protected] “The Android community”? Are we going to put a non-compete rule in writing or spirit for this community? How tone-deaf would this be in the current Reddit upheaval context? The Fediverse is literally about anti-monopilization. [email protected] just so happens to be one community named “Android” among others on other instances. It also happens to be on the largest instance for now. But a successful, large community doesn’t have to be on the largest instance. That’s not how federation works. Ultimately all of us users check the number of user subs before we subscribe or we just sub to all. Being the first to register this community on this instance isn’t what’s gonna determine that. Whichever “The Android community” becomes on Lemmy, it requires moderation work and likely that will determine the final result. If the /r/Android mods want to tell us where the new version of it is, they can do that in a lot more channels than "[email protected]”, like the various tech or Reddit related communities across the instances. Someone posting this here shouldn’t trigger any special feelings in my opinion as it’s no different or significantly more influential. The battle for creating a Reddit alternative is much bigger one than who’s gonna claim they own this or that piece of land. So I’d welcome every free labor team (mod teams) from Reddit to Lemmy and help them get started even if it means that I have to cede some space. We supported these folks during the blackouts, why should we stop doing so when they decided to migrate? Isn’t that the logical continuation of the same events?

About time! 🙌

Related - something I learned during a research course at uni - the shifting of some functionality from software to hardware or the other way around has happened on many occasions. It all depends on how the tradeoffs between performance, optimization, cost and so on shake out.

The hybrid compilation approach is spectacular. Really smart design. It’s as close as having the cake and eating it as possible.

Java performance has rarely been an issue in any environment, Android or otherwise. Recall that one of the most successful mobile OSes running on much slower chips than even the first Android was written entirely in Java - BlackBerry OS. C++ is great too but it requires a lot more competent engineers to do well. Modern C++ is spectacular. Yet often people we interview for C++ positions write C with cout in place of printf.

This name rings a bell. Was that used along with J2ME?

There are many benefits. For example great exception handling. We’re paying very little performance cost for having the conveniences of a managed runtime. Let me flip it, we don’t want unmanaged runtimes, we are forced to run in native, because we need the absolute highest performance in some cases. If the hardware could understand Java bytecode and provide all other JVM facilities, that would have been spectacular. Unfortunately that would be very expensive and pointless as we’ve demonstrated over the decades. If anything we’re moving towards reduced instruction set chips - ARM, RISC-V. And so in many ways the complexity you see is well understood by the folks that have to understand it, it’s well managed, it’s worth it and it’s not at all a performance problem worth tackling.

Did we have to put it on the face of the community? 😄

Pixel as many have suggested. In addition to being able to take any of the popular ROMs, most of the apps on the stock ROM can be disabled.

For example:

It works with multiple languages too. Just tap and slide as if you’re doing a horizontal scroll. Once in that mode, you can keep your finger held down and sliding as long as you want.