This does seem rather self destructive. I guess the brain drain will continue.

It really depends how you see the firmware boundary. You can either treat it as a set of magic numbers you load onto the hardware so it works or see it as an intrinsically programmable part of your system that you should be able to see the source code for or live without support for the device.

I run Circe in Emacs because it's lightweight and integrates with the modeline for not overly distracting notifications.

They are both. There is a non profit foundation which funds the educational side and the main company which operates for a profit. I suspect the bulk of their revenue comes from the industrial side of things where the Pi makes a much better base than a lot of the half assed hacked together SBC's out in the market.

There have certainly been mis-steps asking the way but all in all I consider the Pi to be a British success story. I guess it remains to be seen how much of the valuation goes to the founders and employees and how much is invested into their next phase of growth.

Usually when MPs defect the receiving party tries to find them a safe seat to defend come the election. Otherwise what would the point be?

It's interesting they've gone from a simple reskin to a downstream fork. I'm guessing there won't be much of value to find though.

A bunch of generative filler text won't games more immersive. Maybe there is some scope in giving the model hidden details you need to coax out of it LA Noire style but currently everything seems a bit gimmicky.

Basically your only other option is to find the keys for each BluRay you own yourself. I did go through the hoops a while ago and wrote it up: https://www.bennee.com/~alex/blog/2011/04/18/playing-blu-ray-under-linux/#playing-blu-ray-under-linux

However it's a pain sourcing the encryption keys you need for each disk. While I work hard to prefer FLOSS apps over their propriety equivalents in this case I'm happy to pay the small fee for a perpetual licence of MakeMKV.

A lot of projects would be better served with a plain Makefile although for widely posted projects something is required.

Qemu has used a single readable POSIX shell script for configure although recently most of the tests are in meson (avoiding some Makefile shenanigans in the process). While it's a new syntax to learn at least the intent is clear and reviewable.

curl --upload-file thefile.tgz https://transfer.sh/somename

Then paste the resulting URL to the person who wants the file. Another useful app is the magic wormhole and I think there are some web front-ends for it.

Don't be too hard on Collin. Looking back on the threads it's fairly clear he's been the victim of a social engineering attack on an overworked maintainer. People were pressuring him to hand over maintainership while expressing disappointment at the slow pace of development. The off-list contact by Jia must have seemed like a helpful enthusiastic solution to a burnt out developer.

Hmm don't know why the image gets clipped. Is today a Mastodon or Lemmy issue?

While shell based RC systems do offer flexibility they also have downsides including copy and paste leading to subtly different behaviour across units. Dependency resolution was also a bit of a hack on top of scripts to deal with concepts like run levels.

The declarative approach of a proper configuration is a better and more scalable solution.

So is the theming here for the window decorations or the text colour scheme?

How much theming does a terminal need? Personally my required features were a server and good font support. Currently I use the foot terminal: https://codeberg.org/dnkl/foot

It needs more than that. The NHS has always been a bottomless pit in terms of what it could spend. If we don't as a country invest more in preventive and early interventions it's going to be overwhelmed by an increasingly chronically ill population. We will never be able to throw enough money at the NHS then, especially if an ever larger portion of the population isn't contributing to the economy to fund that.

This seems like an excellent idea and hopefully provides a model for other media outlets to follow.

It is most likely another filesystem mounted where the flatpak can see it. A terminal tool like ncdu or even du will take an -x option to not cross file-system boundaries. That will show the true usage of everything bellow where you call it (even though it is a ramfs so not persisted across reboots).

Don't delete it. It's an area of the filesystem where the current user session data is kept. This includes things like sockets to communicate with other session components and lock files. It's usually hosted on a ram disk so takes up no space in the system and goes away when you shutdown your machine.

Have any actually passed yet? Sure LLMs can generate a lot of plausible text now better than previous generations of bots, but they still tend to give themselves away with their style of answering and random hallucinations.