Well it’s not called easyware

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 never had performance issues, but I don’t read huge books or anything. There seem to be some online converters, but I agree that is not the most ergonomic. Maybe calibre-web could also do the job, with you connecting to it through your phone’s browser.

Never heard about the kepub format but I’ll look into it, sounds cool.

Kobo ereaders are great, when I’m on trips I download epub files on my phone, plug the ereader to my phone via USB, copy-paste the books and it just works. No need to install anything on the Kobo.

Probably wifi, I dont think Moonlight Embedded uses much ram. I also get the undervoltage warning nearly constantly, since the a+ is powered by the usb port of a projector. Maybe that also affects things.

To add more details, I use Sunshine as the server, and stream 1080p, in HEVC for the pi 4 and 5, and h264 for the 3 A+.

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.

Hey you made the claim in the first place, you have the burden proof. Don’t attempt to shift it.

As if American cars had any reputation for reliability XD

I use LibreELEC, it’s great.

This is just the plot to Snow Crash

Podman, rootless containers work well, and there is no central process running everything. I like that starting containers on boot is integrated with systemd.

Kobo ebooks are the best for this, just plug them in a computer and they act as a USB key. Calibre can manage them too. Some models have a SD card slot for a lot more storage too.

Yep, four of them, hence the “Q”.

LLDB?

… iPhone has USB 2.0

Wireless listening absolutely needs more than 2x the power of wired listening. It also needs charging an entire other device. You’re right that it doesn’t affect the phone battery, though I don’t think wireless charging “destroys” it.