mcronce

> Rust made the mistake of thinking it can be low level AND safe. It tried to have the cake and eat it too. That will be its downfall.

Ridiculous take

You think that an LLM provides "love"?

FOSS has been a thing for decades longer than LLMs have even been a vague notion.

You know you can just use a compiled language with statically checked types, right?

I don't think that's a commonly touted benefit of Rust.

You certainly can build a statically linked binary with musl libc (in many circumstances, at least), but it's not the default.

The default is a binary that statically links all the Rust crates you pull in, but dynamically links glibc, the vdso, and several other common dependencies. It's also, IIRC, the default to dynamically link many other common dependencies like openssl if you pull them in, although I think it's common for the crates that wrap them to offer static linking as an option.

For sure. Context switching tasks is certainly a lot cheaper than context switching threads, but it isn't free.

The learning effort thing is a solid point. I think what I play most these days is Super Mario World romhacks. Obviously the level design and whatnot aren't the same as the original, but the controls and physics are and I learned those as a fairly young child in the 90s.

The reason I don't like most other platformers almost definitely isn't because they're actually inferior, it's just because I'm "calibrated" to SMW

...which changes the economics of sending the spam email. Surely some of them will be "valuable" enough to send even with the added cost; however, a measure doesn't need to be 100% effective to be useful.

You're describing rustc_codegen_gcc

It's been a bit since I've added it to an existing project, but at least as of a year or so ago, the Rust implementation (tracing + tracing-opentelemetry + opentelemetry-jaeger specifically for that project) was similar.

The impact on compile time and code size wasn't bad (for a project that was large and already pulling in a lot of crates), but it had a huge runtime cost - mostly allocator pressure in the form of temp allocations from what I could see. For a mostly I/O bound workload, it more than doubled CPU utilization and ballooned OS-measured memory consumption by >30%

It is interesting. A subset of functionally (in this case) will build a superset of programs

It certainly didn't worsen my opinion of the Asahi Linux folks. On the contrary, I commend them for standing up for what they feel is right.

I also doubt they really care whether or not any particular HN reader has a positive or negative opinion of them.

What? All you need to do is resubmit the request without a Referer header. For me, using Firefox, this meant clicking in the address bar, changing nothing, and hitting enter.

That's hardly "no ability to do anything about it".

That's what bindgen is for, as was mentioned in the original comment you replied to.

This follows the "debt" analogy pretty well - it's effectively the interest you have to pay on your technical debt