The_Decryptor

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.

Yeah, the days of end users installing their own OS is in the past, PCs are appliances for most people now.

Yeah I think they’re generally regarded as a mistake, browsers have removed all the UI signifying an EV cert these days.

I wish the tooling around Secure Scuttlebutt wasn’t so annoying to use, more attention might have had some of the rough edges filed off.

On one hand you can have an offline first replication method (Phones syncing messages over bluetooth, etc.), but then you can’t post from multiple devices without moving your account between them.

It’s also not a progressive JPEG either.

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.

It might not have sit well with the fans - he might take a big swing and miss - but at least I felt like he was trying to create art instead of merely making money.

Same, I actually loved how his story had Rey as a “nobody” whose choices and actions were what made her important, SW has way too many special bloodlines, prophecies, and chosen ones.

Then Abrams does a 180 in the sequel 😑

I still hate that god damned dagger.

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)

deleted by creator

How about a 6.4TB sqlite database?

https://boyter.org/posts/searchcode-bigger-sqlite-than-you/

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.

“Fans claim it may offer an improvement” isn’t exactly a definitive statement.

From what I understand the research does actually show little to no improvement for either mode, which is actually a bit odd because we know the eye performs better the brighter the surroundings (Since it causes the pupil to contract, increasing the depth of field)

Maybe it’s a sign that we just need more research into the effectiveness in interfaces.

I take that there isn’t much motivation in moving to 128 because it’s big enough; it’s only 8 cycles (?) to fill a 512 (that can’t be right?).

8 cycles would be an eternity on a modern CPU, they can achieve multiple register sized loads per cycle.

If we do see a CPU with 128 bit addresses anytime soon, it’ll be something like CHERI, where the extra bits are used for flags.

I think CHERI is the only real attempt at a 128 bit system, but it uses the upper 64 bits for metadata, so the address space is still 64 bits.

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.