E

My friend, a podman container file is a simple tiny ini text file. Behind the scenes it gets converted to a systemd service unit file, which is also an ini text file. The service file has a simple ExecStart command that just calls podman run. Meanwhile podman will just set up an environment and run the container with runc or crun. The whole thing is basically one step above a shell script. I could buildroot a system with this entire stack and it would fit on my wifi router.

You’re the one overcomplicating things.

How ironic.

That sounds heavy and complicated.

It’s neither. A systemd generator just transforms a simple 15 line container text file to a simple 20 line service text file, and then the container lifecycle and dependencies are managed by systemd like any other system or user service.

It’s not tightly coupled to anything. It just ships with a systemd generator allowing you to manage containers, pods or networks with systemd if you want. And lots of people are noticing the benefits of that arrangement.

But James Kariuki, the UK chargé d’affaires to the UN, said Britain continues to disagree with fundamental propositions of the text and was “firmly of the view that we must not create a hierarchy of historical atrocities”.

This does indeed invite a whole flurry of what-about comments and resolutions: “Are the Slavs getting a resolution? What about X, what about Y?”

And somehow more “independent” than arch, when it’s based on arch?

I use alacritty with a small script that calls tdrop to make it a drop-down terminal, and sets a few other window properties. For tabs I use tmux as it’s amazing and works everywhere.

It all works perfectly on X, but tdrop is pretty glitchy on Wayland with multiple monitors. Since I use the drop-down terminal a lot, that this was enough of a trigger to move from gnome to kde where I can still use X.

You forgot to include the grandchild and the daughter that were with him and also died.

If you’re Chinese then it’s the other way round, everything outside China takes forever.

What you’re missing is that they want the people to fight them so they have an excuse to attack them more. And these excuses work retroactively too. They bomb, wait for a retaliation, then they say “see, we were right to bomb them,” followed by an even bigger attack. Repeat till there’s nothing left to bomb.

Remind me again why these people hate Iran? They seem to have more in common with the dead Ayatollah than anyone else.

Iirc they only want the difference in tax if you’re in a country where you’re paying less. I’m guessing in most (all?) EU countries you’d pay more, so you wouldn’t need to pay anything. It seems quite sensible.

But at double the price that they were a few months ago.

Ok, I looked into this again, and I think I know what the issue is. It has little to do with summit. Seems like my instance (and possibly some others) convert images to avif while creating proxy images, and I guess android 11 doesn’t support decoding avif properly, or at least my install doesn’t.

Example:
original image, 234k png
proxied image, 11kb avif

I actually tested this by trying different accounts before reporting here, but two things happened that made me reach the wrong conclusion. First, when looking at a different instance which doesn’t use avif, summit will successfully load the images for posts from the cache, so the avif images still got loaded and showed me errors. Clicking retry on the errors actually loads the images normally.
And then secondly, when testing in signed out mode, summit seems to default to using my lemmy.zip instance which again shows the avif images.

Sorry about this.

There used to be x86 Android phones. But they kept that port going even after the phones went away because it was good for development on x86 machines. You could just run a VM instead of having to emulate an arm ISA.

Not even, amd on both my laptop and desktop, but still lots of issues. None of them major, but it adds up.

while they happily stick to the X they know

I mean, I’d love to, but…

Gnome forced me onto Wayland a few weeks ago and I’ve been dealing with issues ever since. Some issues even affecting the most basic level tasks like typing text, imagine dealing with that in 2025. Following your analogy, if the Uber with the fancy new transmission came to a halt every kilometre, you’d care too.

Once in a while, it turns out that enabling -fms-extensions could allow some slightly prettier code. But every time it has come up, the code that had to be used instead has been deemed “not too awful” and not worth introducing another compiler flag for.

That’s probably true for each individual case, but then it’s somewhat of a chicken/egg situation.

If we just “bite the bullet” as Linus says and enable it once and for all, it is available whenever a use case turns up, and no individual case has to justify it.

A lore.kernel.org search provides these examples:

• https://lore.kernel.org/lkml/[email protected]/
• https://lore.kernel.org/lkml/[email protected]/
• https://lore.kernel.org/lkml/[email protected]/
• https://lore.kernel.org/lkml/[email protected]/
• https://lore.kernel.org/lkml/CAHk-=wjeZwww6Zswn6F_iZTpUihTSNKYppLqj36iQDDhfntuEw@mail.gmail.com/

Undoubtedly, there are more places in the code where this could also be used but where -fms-extensions just didn’t come up in any discussion.

Basically the extensions are useful sometimes. Note that they have nothing to do with Microsoft other than being invented by them.