The_Decryptor
spoiler
made you look
- 0 Posts
- 35 Comments
25·25 days agoAs 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 always been an option (iirc called “Global Menu”), it only works with apps that specifically support it though (Either through Qt or custom support for GTK apps) so that’s why it’s not the default.
1·2 months agoTrue, they removed the aliases in Core, but left them alone in the bundled version since much like base
cmdthey’re not updating it anymore.
I’ll never forgive them for aliasing curl to Invoke-WebRequest instead of the real curl.exe.
At least they walked that one back, by just shipping curl with Windows.
It’s more like QEMU actually.
TypeScript is actually pretty nice, it’d be JScript instead.
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.
2·4 months agoThat’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)
8·4 months agoFor a while Google let you blacklist domains from search results, fantastic feature so of course they killed it off.
How about a 6.4TB sqlite database?
They’d run afoul of the whole “editing your own article” restrictions.
Those chips not supporting RV23 isn’t super surprising, they were released in 2023 while RV23 was only ratified in 2024.
Ubuntu requiring RV23 however does surprise me (I admit I didn’t read the article), that seems premature, but I suppose it’s a good baseline going forward. Last time I looked at any of the chips none of them supported the V extension, and those that did were majority only supported the incompatible pre-standard version.