I hope that the language’s ints are at most 32 bits. For 8 bits it could even be written by hand & the source code for a 32 bit version would only take up avg_line_len * 4GiB space for the source code of the function. But it might take a bit of time to compile a version that supports the full range of 64 or 128 bit ints.

They’re on the feddit.uk instance, so it’s more likely that they’re British. Either their VPN prefers USA servers for some reason, or they’ve only done about 138 million downloads at most.

What’s disgusting about it? The only thing I can think of is the implicit return, which felt a bit icky at first.

Also, as the if expression is an expression, you can call methods on it like so:

if 1 > 2 {
    3
} else {
    4
}.min(5)

(the above is still an expression, so it could be used, for example, as part of a condition for another if)

Of course, you can write horrible code in any language, but the ability to use blocks where expressions are expected can be great sometimes.

Rust would allow you to

let ret = if some_condition {
    <a lot of expensive calculations>
    result_of_operations
} else {
    <a lot of other different expensive calculations>
    result_of_other_operations
};

Now you don’t have to declare it inside the blocks.

It’s way more common than you may realize. Intel & AMD (and other x86 CPU manufacturers of the time) did it before the first Crusoe CPU launched. (2000 according to Wikipedia)

CISC architectures are now seen as inefficient, so all the new ones are RISC and new CISC CPUs just translate the instructions to their intenal RISCier microarchitecture. The CPU’s microcode specifies what an instruction translates to.

A communication protocol used in microchips, small modules & embedded devices that uses 2 wires. Think something like USB, but dead simple.

CSS can actually do a lot. Many effects that are often done trough JS can also be done with CSS.

Don’t forget Self, the type of self.

I’m currently traveling through time at 0.00027̅ h/s.

What about μc or nc, a bit umder 300m/s & 3m/s, respectively.

How would other types of taxes, like in you example, gift tax, be handled?

Huh, really? Do you remember where you read this?

For such large registers, I think error correction for the error correction might be useful.

But something could easily go wrong with such large registers & access would be slow. Maybe we should have RAID 1 for registers?

But many people don’t use any of those features. I get that many do, but every single smartphone with features I require has them.

Oh no, I think I might’ve missed my chance, then.

But seriously, I have abslutely no use for a “selfie camera” & feel uncomfortable with the whole concept of having a camera constantly facing you. At least with laptops it’s easier to put something in front. Even with a back-facing camera, its use is very limited & would prefer to be without one, let alone a handful.

I agree, cars are invasive & devastate local wildlife. But they don’t belong inside, either.

It’s being built up starting with the foundations. As I understand it, most of the work so far has been adding support for Rust-written GPU drivers into the kernel. I’d guess that they’re going to look at Nvidia’s open kernel drivers to avoid reverse-engineering everything, but it seems like they’re not just copying it. Unlike both official Nvidia drivers, NOVA will talk with the NVK Vulkan driver in Mesa, not Nvidia’s closed userspace drivers. This will likely make it more compatible with parts of the Linux ecosystem that Nvidia has historically had issues with, like Wayland. Even if they don’t look at the official open driver, NOVA will be a lot simpler than Nouveau, as it only supports GPUs with a GSP, to which Nvidia has moved a lot of the magic that used to be in the kernel driver.

What about RFC 3339? It’s technically different.

camera phones

Why are all “modern” phones so full of cameras? One on the fucking screen & at least 2 on the back. I just want a phone with no cameras. Even 1 might be O.K., so long as it’s on the phone’s backside.