Containers kinda are the opposite of serverless, not surprising they don’t have that in their instructions.

Impossible Creatures was so much fun, especially with friends. I also thought Age of Empires III was very good, even if it was pretty different from II.

Show how much he knows, if he thinks her baby is in her placenta.

Yeah these batteries are like 95% recyclable

Cool, do Trump next!

Homarr supports all of that iirc

Edit: Just saw it doesn’t appear to support rootless, that sucks, my bad

Contrary to the other commenter, I AM trying to say you’re wrong. Universal healthcare is very much possible, see every actually developed country! They even managed to do it without the molten lead thing, though I’m sure it would help.

Fewer steps actually, since it is built into the kernel

Because they are?

Aka no one in French would call them dandelion

Yeah that’s what I meant, around here everyone calls them pissenlit, hence piss the bed.

Dandelion also means pee the bed in French, might be on to something.

Well it’s not called easyware

It’s the look of too much HDR

And the fact that you need to create a wrapper means that some programmers won’t bother to do it, or won’t know they need to do it. The default case handling timezones correctly will reduce potential errors.

You should look at it, they say the implement RFC 9556 timestamps, which include tz info. In my experience it IS useful in real use, because a fixed offset timestamp can lose a bit of information.

For example, if you have a timestamp and want to add a few months to it, for example for a reminder, you will get a timestamp at the same time in the same offset. In many cases that will be wrong, because of things like daylight savings time, which change the offset of the timezone. You will get a timestamp an hour before or after the moment you intended, and it will be in the “wrong” offset in that timezone in that time of year. With timezone aware timestamps, they are aware that the offset will change, and will be able to give a timestamp in the future at the correct time and offset.

In this section, wouldn’t be more realistic for chrono users to use timezone info around the wire instead of on the wire, rather than using Local+FixedOffset?

They do say that the difference is that chrono users would need to keep out-of-band timezone information in addition to the datetime, whereas Jiff does it in-band.

I have a Surface Go 1 with 8 GB RAM running Aurora-DX, which includes the linux-surface kernel. It works great, and I find that modern KDE works quite well with touch, even though I mostly use it with the type cover attached. I only use the surface connect port for charging, but I do use the single usb-c port with a usb-c hib, and it works well. The Fedora atomic distros work great on little machines like that.

Edit: I’d add that Bluefin is the same with Gnome.

I use Moonlight Qt on a raspberry pi 5, and used it on a raspberry pi 4 before that. Both connected via ethernet, streaming at 150 mbps. It works very well, feels like being at the computer. It feels like there is next to no delay, and moonlight reports around 5 ms.

Somewhere else I use a raspberry pi 3 A+ with Moonlight Embedded, connected via Wi-Fi, and it works pretty well, but I can notice the delay a bit more. Still able to stream at 40 mbps.