Because google doesn't want you doing anything that they can't controlfun on the host Android system. They did the same thing with crostini on ChromeOS for "security".
The people complaining that Apple copied a good thing are missing the point. If Apple includes containerization on macOS by default (even if you have to enable it manually), more developers can just target Linux instead of Linux and macOS for certain types of applications (real bash scripts with GNU coreutils instead of the trash that Apple ships, servers, etc.).
Looks like they're jumping from 15 to 26, in fact they're doing the same thing for iOS, jumping from 18 to 26 for the next release. Looks like they're synchronizing all their OS version numbers using the year they'll be primarily used(i.e. 2026) from what I can find.
This is my preferred versioning format for user-facing software, by far.
I feel like Semver should also adopt the date inclusion, like 7.4.2-202606 or even 7.4.202606 — you can even extended it to multiple daily releases like 7.4.20260610.1233
There's too much software to mentally track when each version was released. You should be able to tell at a glance.
Darling is a cool project but I think the reason it hasn't taken off is because there isn't a lot of software people both want to use on Linux and software that isn't already covered by wine. You need an overlap between those 2 and that's a small market
Yeah, I just think that maybe, just maybe, if MacOS is also inspired by UNIX, making a compat layer is not that big of a difference. Because MacOS supports a lot of productivity programs that may attract professionals to Linux too. Mostly adobe suite.
Wine is successful because of the decades of work put into it. For Darling to reach that level of support it would need a herculean amount of effort as well.