The_Decryptor

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)

deleted by creator

For 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?

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

They’d run afoul of the whole “editing your own article” restrictions.

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.

Best way forward if they so insist is to refactor small bits without interfering with the existing code-base.

I’m not sure they’re even doing that, I think the policy is that Rust code can depend on C code, but C can’t depend on Rust. So at the moment nothing can actually be rewritten in Rust, it’s only additions like new drivers.

On a more serious note, having a CTO at Microsoft, of all places, jump in on your side is kind of embarrassing.

That comment was from a few years ago and wasn’t in relation to Linux, and the company he co-founded made some pretty useful things (And revealed the Sony rootkit in 2005) before MS bought them.

NTFS was designed back in the mid 90s, when the plan was to have the single NT kernel with different subsystems on top of it, some of those layers (i.e. POSIX) needed case sensitivity while others (Win32 and OS/2) didn’t.

It only looks odd because the sole remaining subsystem in use (Win32) barely makes use of any of the kernel features, like they’re only just now enabling long file paths.

Yep, Apple paid with shares (More specifically, the right to buy $1 million dollars worth at the initial share price) which, according to a share calculator I just tried, would be worth nearly $328 million these days, I wonder if Xerox kept them or offloaded them early.

Considering Xerox was utterly uninterested in any of the tech they had, it’s worked out well.

If you think the comments about Rust are bad, you should check out any article about X11/Wayland or systemd.

Stuff that’s spec compliant has to follow the rules, non-spec compliant stuff can obviously do whatever, so yeah the cheap cables off ebay or amazon won’t use the right logos.

It’s USB2, so either for charging or simpler devices that don’t need USB3 (Like keyboards).

Edit: Federation issue? I swear there wasn’t an existing reply when I responded.

Better, kid friendly urban infrastructure like dedicated bike paths protected from car traffic, better pedestrian areas, parks and so on. Kids will get outside their house if there is a kid friendly outside. A greener, more human friendly outside where you can socialize with other humans would always be preferred over doom scrolling online.

Good luck with that, people and politicians love cars, parking lots and highways, and the media is demonising kids as criminals.

Qt is overkill if all you’re using it for is to create a window you render into, something like SDL would be better.