Cricket@lemmy.zip

Right, I figured that that was probably what Waydroid was. However, I also figured that it does the translation of ARM code to x86 hardware. Is it capable of skipping that translation entirely to run ARM code directly on ARM hardware as it is now? Does it work well? These are the things that I was entirely unsure about because I’m not very familiar with Waydroid. If you know the answer to these, I would love to hear it.

Wouldn’t there be at least some Android APIs that they would need to handle too? I wouldn’t expect Android APKs to work natively on Linux even on ARM, but perhaps Valve has already addressed that.

Right, I’m trying to wrap my head around the idea that Waydroid does some kind of ARM emulation on x86, but now we’re talking about ARM software running on ARM hardware. Can Waydroid itself do this if it’s run on ARM hardware?

Not a video of a Valve employee, but I’ve read at least a couple articles now quoting Valve as saying it will support Android APKs, although I can imagine that this kind of thing could easily be misinterpreted due to some technical detail. This article mentions it: https://www.theverge.com/news/818672/valve-android-apps-steam-frame

Valve says the Steam Frame can use the same Android APKs developers already use to bring their apps to phones and Android-based VR headsets such as the Meta Quest — and it’s launching a Steam Frame developer kit program to help put the hardware in developers’ hands.

It sounds like Valve is specifically hoping to attract some of those Meta VR game developers, rather than just any kind of Android app you might find on a tablet or phone. “They’re really VR developers who want to publish their VR content, and they’re porting a mobile VR title where they’re already familiar with how to make those APKs,” says Selan. “They are now free to bring those to Steam, and they’ll just work on this device.”

The actual quote mentions porting, and the non-quote claims they’re saying “same Android APKs”. It definitely sounds like it could be a misinterpretation of what was said, which is disappointing for a popular tech outlet like The Verge.

Edit: now this video has a Valve quote saying (at 26:03) that APKs will be sideloadable like Steam Deck apparently already does. They also say that they expect VR APKs to work if they don’t use proprietary APIs. https://www.youtube.com/watch?v=bWUxObt1efQ

Good points, and I agree with all of it. I definitely remember all the talk about becoming a “service economy”.

Don’t some people think that it started even earlier than that, when we abandoned the gold standard? I always saw that as some kind of crank theory, but nowadays I’m not so sure. I haven’t looked at that debate much in depth though.

It will limp along on financialization and debt.

I’m far from an expert or even very knowledgeable about economics (never taken macro or micro economics), but hasn’t that been the case for decades?

Where Google’s team put innovative effort into ChromeOS was in making it robust enough to be sold to the masses in the hundreds of millions of units, with no tech support. It’s immutable, with image-based updates. It has two root partitions, one of which updates the other, so there’s always a known good one to fall back to if an update should fail.

Vanilla OS also uses a two root partition system, called ABRoot, for its atomicity. The author should look into that, as it seems to be exactly what they’re looking for.

This is a more fault-tolerant design than SUSE’s MicroOS-based systems, which use the rather fragile Btrfs. It’s also much simpler than the Fedora Atomic immutable systems, including offshoots such as Universal Blue, which use the Git-like — for which, read “fearsomely complex” — OSTree. For added entertainment, Fedora also defaults to Btrfs, with compression enabled. If you don’t believe us about the problems of damaged Btrfs volumes, refer to the Btrfs documentation. We recommend taking the orange-highlighted Warning section very seriously indeed.

Stupid fearmongering about BTRFS (and OSTree, I presume). I selected an OpenSUSE distro precisely because it uses BTRFS and Snapper for automatic and transparent snapshots by default, which simplifies undoing most things that can break a system.

Very intentional. My recollection is that they hijacked the ISO committee to adopt their 6,000 page specification(!). This 2008 article briefly touches on some of the controversy, but I recall reading about the drama on Slashdot for months: https://www.ip-watch.org/2008/04/01/office-open-xml-officially-approved-as-international-standard/