Worse, surveillance appliances. Highly likely we'll see mandatory client-side scanning apps in EU soon, and possibly Digital ID stuff in the UK.

Great opportunity for mandatory remote attestation and mandatory software.

Qualcomm Arm PCs support hardware nested virtualization for pKVM L0 and KVM L1 hypervisor, similar to Pixel devices. This could enable Debian Linux in a VM, currently available on Pixel as "Linux Terminal" for developers, with all Debian Arm packages and root access in the VM.

"Terminal app can now run full graphical Linux apps in the latest Android Canary", https://news.ycombinator.com/item?id=44681858

"Coding without a laptop: Two weeks with AR glasses and Linux on Android", https://news.ycombinator.com/item?id=43985513

They decided it'd be more efficient to make one thing worse than two at the same time.

I would suspect that they continue to support those until they hit their agreed upon EOL. At some point they will ship new units that are essentially identical in use (running chrome), but are locked down under the hood (for school use) to be more like chromeOS and less like Android.

There is a good chance the average end user wont even notice the difference. It seems doable, but I guess the devil is in the details. If they can't pull it off, Apple is rumored to be launching a ~$599 macboook. Would not be really stretch to see them complete in this space again in the future.

They see an entrance into the windows desktop market and they are taking it. I personally like this path because the only good laptop+phone integrated combo I see is from Apple. Hope they don’t screw up on opportunities like clipboard sharing and other integrations.

I think ChromeOS has been slowly making the merge for awhile now, hence the chrome store being killed and replaced by the android store. Everytime I updated my Chrome book over the past year or so it gets a bit more android like.

ChromeOS support is contracted and thus guaranteed.

But one day they'll have to switch, when the support runs out. IIRC it's 7-10 years depending.

It's pretty bad. The only place it sort of thrives is Amazon's tablets and android ereaders.

They are all (AFAIK) based around android 9 or 10.

You are seriously almost better off just doing something like a windows tab converted to a linux machine.

I am on a Samsung Android tablet

I've got a Lenovo tablet. It's bad - I only use it to read music and it's so laggy. It was cheap but I feel I'd have been better off getting a used ipad.

> Android tablet market basically on life support

I dont think so, it's more active recent year. There are a lot of good Chinese tablet(from well known brand). Xiaomi, lenovo, vivo, oppo and oneplus all have "flagship" tablet(running high end CPU, with very good screen and build quality)

Nope, because outside US, where Android dominates, most folks also go for an Android tablet, between Samsung, Xiomi or Huawei.

I think usually people that only see iPads around come from the few markets that are dominated by Apple.

I think in general their plans are contrary to the DMA if they prevent F-Droid from existing. The big bet seems to be that Trump can coerce the EU into repealing the law entirely.

> (50) [...] In order to ensure that third-party software applications or software application stores do not endanger the integrity of the hardware or operating system provided by the gatekeeper, it should be possible for the gatekeeper concerned to implement proportionate technical or contractual measures to achieve that goal if the gatekeeper demonstrates that such measures are necessary and justified and that there are no less-restrictive means to safeguard the integrity of the hardware or operating system.

> (54) Gatekeepers can hamper the ability of end users to access online content and services, including software applications. Therefore, rules should be established to ensure that the rights of end users to access an open internet are not compromised by the conduct of gatekeepers. Gatekeepers can also technically limit the ability of end users to effectively switch between different undertakings providing internet access service, in particular through their control over hardware or operating systems. This distorts the level playing field for internet access services and ultimately harms end users. It should therefore be ensured that gatekeepers do not unduly restrict end users in choosing the undertaking providing their internet access service.

https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%...

  $ c2w ubuntu:22.04 out.wasm

I love termux, but it's really not a replacement for full fat linux. There's tio many incompatibilities with how linux software expects to run for it to work for a dev workflow (unless your workflow is to immediately ssh into something else).

The most compatible setup I found is proot-distro into alpine, which bypasses a lot of the android blockers, and the bionic-libc incompatibilities by using musl. Comes at a performance cost, however.

I'd guess that these will support their virtualization framework so that you don't have to depend on tmux.

Android Terminal works pretty well on the pixel at the moment, so hopefully the merged version in ChromeOS-style laptops and tablets will be fully usable.

> I can live inside termux but there are things termux struggles to do,

Because that isn't part of the set of allowed NDK APIs.

https://developer.android.com/ndk/guides/stable_apis

Anything that termux manages to do outside of that list is more out of sheer luck that Android team hasn't closed down that specific Linux syscall.

Initially Android only got the NDK back in Android 2.0, due to pressure from game developers, and Dalvik having such a lame performance, it was never for writing full applications.

I mean, Pixels run a "desktop mode" today if you enable stuff in dev options and connect a display, keyboard, mouse via USB.

Not a stretch to imagine that its the same work, so its desktop android, not, ChromeOS merge, this time.

Android on Windows?

Fuchsia actually continues to receive hundreds of commits per week and is under VERY active development including moving into Android itself (although fuchsia itself remains uncoupled to Android and cna be used in other contexts)

Fuchsia is DoA. They tried moving nest and smart speakers to it and scrapped the project in 2023.

I think it matters what "support" means.

This could be the "next generation" ChromeOS that are exclusively available on new/recent Chromebook devices, while Google keep updating the "legacy" ones with only security patches. From what I can tell, Google never explicitly promised that every supported Chromebook can get the latest feature updates. The only said "updates".

Of course this is pure speculation and I'd love to be proven wrong.

AFAIK a majority of Chromebooks are x86 (which has always been funny to me because surely that's the best case for ARM but w/e). Therefore, I think it's reasonable to assume that any new ChromeOS-on-Android OS will probably run on x86. Now I grant that x86 Chromebooks are already not using normal UEFI so there is a small gap there... but if you're already building the same OS for the same CPU on basically the same hardware, surely it's worth the... what, couple days of work?... to add an UEFI bootloader to vastly increase your hardware coverage. For bonus points, this should make it (even) easier to run in VMs for dev reasons.

All of which to say: Yeah, I'm actually somewhat optimistic that we get official Android x86 out of this.

It did, yeah. A merge the other way would have probably been a bad idea too, they should remain separate.

China in happening.