made you look
As I was doing that, I also thought I’d message the vendor and ask them if they could share any specifications or docs regarding their protocol. To my surprise, Nanoleaf tech support responded to me within 4 hours, with a full description of the protocol that’s used both by the Desk Dock as well as their RGB strips.
Now that is cool.
And on the upside for them, no Gnome, since the devs are making systemd a hard dependency.
I am entirely unsurprised that people who hate systemd also hate wayland.
Then there’s accessibility functions, which wayland breaks almost by design by denying apps access to each other. Even something as simple as an on screen keyboard becomes nearly impossible to implement.
That’s a side effect of just dumping everything into X11, once you switch from it you lose all the random kitchen sink warts it grew over the years.
Like an on-screen keyboard shouldn’t be fiddling with a display protocol to fake keyboard inputs, it should be using the actual OS input layer to emulate them (So then it’d work with devices that read input directly and not go via X11). Same with accessibility, there’s a reason other OSs use separate communication channels with their own protocol.
It’s more like QEMU actually.
TypeScript is actually pretty nice, it’d be JScript instead.
Yeah, I think Windows actually handles it quite well, the actual filesystem has no notion of what the filenames are outside of basic “It’s UTF-16”, it’s the OS filesystem layer that handles all the quirks.
Because that’s what people seem to dismiss, there’s no one standard notion of case folding. It depends on the locale you’re using, and that shouldn’t be built into the FS itself. The classic one was the German “long S”, where “SS” should be case folded with “ß”, except they changed it in 2024 so now they shouldn’t match (“ß” becomes “ẞ” now), good luck updating your FS to support rules like that.
Now your shell? That’s easy, you can just warn the user that a “matching” filename already exists and prompt them to change it, and you can vary those warnings based on the locale, and you can push out updates as easily as any other patch.
Guessing you used this page for that?
https://tools.myfooddata.com/nutrient-ranking-tool/Choline/Nuts-and-Seeds/Highest
Try adding the “Vegan” option, and it’ll list 91 food types that contain more choline by weight
2011? That’s basically last week right?
Support for it (and UEFI ) came with their push into servers, they were forced to make the platform a lot less special and more general purpose like x86 traditionally has been.
End user facing hardware is a different matter though, like I know you can boot the Raspberry Pi via UEFI/ACPI (It builds the ACPI tables in the bootloader), but then Apple doesn’t use it at all for their ARM hardware and it uses something closer to a modern OpenFirmware.
I think x86 is basically the only platform that’s used ACPI, other hardware usually ships a fixed hardware list in firmware that the bootloader/kernel can read (Since it’s not like the motherboards are modular, e.g. the RTC is never going to randomly be connected to a different controller)
Historically ARM didn’t even do that, it was mostly used in tightly linked systems so you’d just build those assumptions into the software itself (e.g. a Gameboy always has a directional pad on specific pins, so you just read those pins directly) I remember the early days of the Raspberry Pi involved device dependent kernel images because they had to code the specific initialisation routines into the drivers, it took a while for them to gain “device tree” support so you could have a generic kernel.
That’s “Extended ASCII”, basic ASCII only has upper and lowercase latin characters and things like <, =, >, and ?
And probably half of the control codes are still used, mostly in their original form too, teletype systems. They’re just virtual these days.
A place I worked at did it by duplicating and modifying a function, then commenting out the existing one. The dev would leave their name and date each time, because they never deleted the old commented out functions of course, history is important.
They’d also copy the source tree around on burnt CDs, so good luck finding out who had the latest copy at any one point (Hint: It was always the lead dev, because they wouldn’t share their code, so “merging to main” involved giving them a copy of your source tree on a burnt disk)
How about a 6.4TB sqlite database?
A single user mastodon instance has the same issues, any hashtags you can see will be from users you already follow. You need to subscribe to a relay to see more posts (Which GTS actually currently doesn’t support, so you need to follow tags from something like https://relay.fedi.buzz/)
Using a PCI screw bracket as a bottle opener
I assume it’d be used for high quality time synchronisation, when you’re running your own time servers.
So you’ve got a system synced to a GPS unit, and sends it’s time to other devices on the LAN via PTP. This would help the system account for latency between the CPU and NIC, I assume.
I think the biggest issue would be a lack of interfaces to the C side code, they’re slowly being fleshed out and each one enables more functionality for the Rust modules.
e.g. the test Ext2 driver a MS dev wrote last year after enough of the filesystem interfaces got hooked up
But even then, I don’t think the maintainers would accept one that replaces the existing C driver, that’d break non-Rust builds and architectures, and that’s a sure-fire way to get Linus on your case. Best you can hope for is one that complements a C driver, and even then I think you’d need a good reason to have two drivers for the same hardware.
Or Automattic doesn’t have enough employees left to implement it