It was kind of pointless, but at least it made software work with custom default branches.

Considering Samsung seems to use WatchOS: Build a Watch face | WatchOS

I mostly use Jetbrain’s IDE’s and NeoVIM when changing configs through the terminal.

Sounds very appropriate for a government operation

I doubt the little green men have the same 2 “immutable genders” as humans may have, so I doubt they can get the required papers under the current administration.

I know this was supposed to be a joke, but you didn’t really succeed judging by the comments. Perhaps try less sarcasm next time.

…

Keep in mind that in practice this didn’t work that well, it wasn’t very efficient at displaying modern interfaces over the network. Showing a simple text editor over LAN worked fine, but using Firefox from another place was quite spotty.

That actually seemed quite useful at first.

That’s unlikely, the additional R&D cost probably won’t weigh up to the costs incurred by the small minority that removes it.

It works well when you want to install software that is not compatible with your distro, but it is not a great security measure since it integrates with your host system instead of acting as a sandbox.

Isolation and sandboxing are not the main aims of the project, on the contrary it aims to tightly integrate the container with the host. The container will have complete access to your home, pen drive, and so on, so do not expect it to be highly sandboxed like a plain docker/podman container or a Flatpak.

This is just incorrect

…or containers, e.g. Docker/Podman

Distrobox is a script that manages Docker/Podman containers

What you are installing can cause damage so IMHO it’s more about keeping things manageable while having your actually important data…

Programs are installed the container, not on the host system. When you break the container the host system is fine unless using rootful (or Docker) containers.

…while having your actually important data (not programs, downloaded content, etc but rather things you did yourself, e.g. written documents, sketches, configuration files, prototypes, photos, etc) safe…

Using Distrobox does NOT keep your own files safe, it actually mounts your home directory and external USB drives inside the containers by default fully exposing your documents to whatever you install inside.

From the documentation:

Isolation and sandboxing are not the main aims of the project, on the contrary it aims to tightly integrate the container with the host. The container will have complete access to your home, pen drive, and so on, so do not expect it to be highly sandboxed like a plain docker/podman container or a Flatpak.

Corrupt the training data with illegal numbers

Write some kernel stuff in Rust and then see what happens in a few years time.

I think that’s what people are trying to do by writing drivers. To me, they seem like a perfect candidate for trying out Rust, they’re less tightly integrated from other parts of the code and preventing faults which can cause instability / security issues seems like a high priority. However, the code needs to integrate somewhere so bindings have to be written and it seems that is being blocked.

Assembly wouldn’t be viable because it requires rewriting for every architecture, C is the closest to assembly there is while still working on all architectures.

The original entry from the mailing list this is all about:

On Wed, Jan 29, 2025 at 10:33:22PM +0100, Danilo Krummrich wrote: I accept that you don’t want to be involved with Rust in the kernel, which is why we offered to maintain the Rust abstraction layer for the DMA coherent allocator as a separate component (which it would be anyways) ourselves.

Which doesn’t help me a bit. Every additional bit that the another language creeps in drastically reduces the maintainability of the kernel as an integrated project. The only reason Linux managed to survive so long is by not having internal boundaries, and adding another language complely breaks this. You might not like my answer, but I will do everything I can do to stop this. This is NOT because I hate Rust. While not my favourite language it’s definitively one of the best new ones and I encourage people to use it for new projects where it fits. I do not want it anywhere near a huge C code base that I need to maintain.

Equinix seems to be shutting down their bare metal service in it’s entirety. All projects using it will be affected.

A system daemon to allow session software to update firmware

(In case I’m not the only one who hasn’t heard of it)

Paid apps are in the works right?

Linkwarden can manage links and automatically archive the page as PDF, image, and/or HTML/CSS