I think the main thing holding Wayland back are older drivers which don’t work well with it and impact on things like games. Once its over that hump there isn’t much reason for maintainers to suffer two back ends any more.

I’m laughing that the committee awarded the prize to a Venezuelan. Trump is going to be raging all day - all caps screeching about how he deserved to win, how Maria Machado is a loser, about how many conflicts he resolved etc. His government is going to be striking out against Venezuela (despite the winner being an opponent of the regime), Norway and the Nobel Prize organization. Fox will be on a rage fest too and all his proxies too. I guarantee that we’ll see esteemed members of Nobel getting detained at US borders, being deported etc because Trump is a sore loser little bitch.

Why the fuck should they hold a minute’s silence for this piece of shit anyway. He was an asshole in life, he got shot for his troubles and now the far right are trying to make a martyr of him Horst Wessel style. And that includes some some fellow traveller who happens to be an MEP in this instance.

You think if they used another licence it would be any different? Countless open source projects have a GPLv3 + proprietary licence which is way more evil than Apache - they poison the open source with GPLv3 so no competitor can contribute without revealing their changes while they themselves can use the proprietary licence. e.g. Trolltech and QT for example but there are many others.

And frankly you should be blessed that you have a fully fledged, open source phone OS you may fork and build from. The OP wants a Linux phone OS and AOSP is a Linux phone OS. There are many forks of Android, closed and open that wouldn’t exist if Google had just decided to be proprietary from the get go. They were under no compulsion to do this but they did. If you have used LineageOS, or GrapheneOS for example then you are a beneficiary of this. You are completely at liberty to have a de-Googled modern phone OS powered by Linux right now.

Wait… they opened it so they can close it?

Android is Linux. It uses a Linux kernel paired with a BSD based user land. Also there is an AOSP version of Android which is Android without all the Google bits. LineageOS and some other security oriented firmwares derive from it. That isn’t to say Google are necessarily happy about this entirely but at the same time, they open sourced most of Android and probably see it as a useful antitrust defence and the impact of flashed devices barely more than background noise.

The issue of bootloaders is an orthogonal matter since Linux or not does not mean bootloader or not - many black box devices use Linux but you won’t be flashing them any time soon - TVs, set top boxes etc. I would argue that regardless of OS, there should be a right to repair law (e.g. in Europe) that allows people to maintain devices beyond their warranty. And if Samsung et al don’t want to do it, then they should have an obligation to unlock devices upon request.

Some people just don’t appreciate the irony of killing turtles with fish-shaped plastic, what can you do

PLA isn’t food safe in 3d printing mostly because of layers on a print trap foreign material / bacteria and water can also seep into microscopic gaps into infill and it becomes a breeding ground. I doubt it would be useful for anything squeezy but it might be useful for single use forks and other utensils. But paper / wood can do those things already so I don’t see PLA being much use. For sachets I expect the answer is paper with some kind of biodegradable lining which gives a product a shelf life of a few years but does degrade in time.

Also, some “biodegradable” products are only compostable in specialist facilities where it can be shredded and broken down with water / heat / pressure. I think PLA is a bit like that. If you print something out of PLA and stick it out in the garden or even toss it into a compost bin it’ll still be there in 10 years although it might be faded, warped & brittle. Maybe it eventually biodegrades but it’s not quick enough.

I’ve never seen these things before but it does seem like a waste of plastic. Even sachets of sauce shouldn’t be handed out in most circumstances, at least for dine-in food in fast food places - use dispensers and paper cups. I wonder if there is a biodegradable sachet material which has a couple of years shelf life but degrades thereafter.

I don’t really buy the “small incompatibilities” argument. The project strives for total compatibility, even down to the most esoteric parameter that nobody has ever heard of. And even that seems like overkill to me - there are alternative implementations of core commands on Linux and other *nix systems like BSD, Solaris etc. where the compatibility is way worse. For example, busybox is used in embedded Linux, and a containerized images like Alpine Linux.

It also seems a bit rich to complain that uutils might get extended. GNU coreutils came into being because of dissatisfaction with the commands that came with the default *nix. Same for bash (vs sh), GNU cc (vs cc), GNU emacs (vs emacs) and so on. Was there somebody back then complaining about devs “spamming commits” that extended functionality?

And other Rust applications won’t only work with uutils. That’s absurd. They’ll test the capabilities of the OS they’re built to run on either at build time with feature flags or at runtime by probing commands. Just like any other high level application.

As for license, MIT is used for plenty other things in a typical Linux dist, e.g. X11.

The biggest point of concern for a Rust rewrite is dependency integrity. Rust uses cargo to manage dependencies and absolutely everything in the Cargo.toml/Cargo.lock files has to be reviewed. The crates.io repository is beginning to support package signing and The Update Framework initiative but every single dependency of uutils would need to be carefully reviewed and signature validated for it to be considered trustworthy. Basically everything needs to get locked down, and wherever possible dependencies expunged altogether.

It’s funny watching rapey getting ratioed on his own echo chamber platform.

Soon these oligarchs won’t even own a window to jump out of

While I wouldn’t want flakpak going deep into the OS I think the advantage of using them on the desktop is obvious. Developers can release to multiple dists from a single build and end users get updates and versions immediately rather than waiting for the dist to update its packages. Plus the ability to lock the software down with sandboxes.

The tradeoff is disk consumption but it’s not really that big of a deal. Flatpaks are layered so apps can share dependencies. e.g. if the app is GNOME it can share the GNOME runtime with other apps and doesn’t need to ship with its own.