These days though you can just breakpoint()

They have been trying to work with the Flatpak people to make it a standard everyone could share. After half a decade of frustration I think they just gave up and decided to do it themselves.

I’m not the person you replied to, but I would love to have more ARM hardware for running tests on. A lot of what I write needs to be separately tested on each architecture.

The other LTS kernels didn’t get it until yesterday, and this thread has some good info about why: https://infosec.exchange/@wdormann/116489443704631952

Yes, both.

The architecture is really varied. You can get super cheap SoCs that are barely capable of running FreeRTOS, and you can get 100+ core beasts with EFI, PCIe, etc.

I’m pretty sure Microsoft has more people working on Linux stuff than Canonical has total employees.

Some Canonical employees are working on it but it’s not originally a Canonical project.

Hopefully their plan for software sovereignty includes using a European desktop environment.

That’s a systemd slurpee.

Try putting it on the speaker’s nose and jiggling.

Right now Asahi increases the value of ARM based Macs slightly since there’s another market of people who will buy them.

Once Asahi means that people can keep end-of-life ARM based Macs running, the calculation for Apple will change.

Open source, mainline PowerVR drivers are a huge step forward for practical RISC-V machines.

It’s not that iOS is unsupported. It’s just that they prohibit browsers from implementing the features my webapp needs.

Yeah, it’s pretty much that Fedora is to Red Hat as Ubuntu is to Canonical. RHEL vs. Ubuntu Pro work a bit differently though.

This is why I built my own CPU from sand and a RISC-V specification sheet.

A distribution with first class KDE support, obviously 😛

Just another reason not to use Mint.

Heh you’re right, I didn’t catch the bitwise and, so I thought you were making a TypeError joke about comparing strings. Fixing the and though (which I did naturally when I typed it into my interpreter to double-check), we get the issue that they are just using a string for the time rather than a time object. “Too early” is also a valid entry that gets us an available office.

Idk it works for me.

Also "8:00:00" > "10:00:00"