HN user

mcronce

1,005 karma
Posts0
Comments358
View on HN
No posts found.

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.

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

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 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".

Even if the bus/protocol is limited to "only" disk I/O, you could still have the controller interpret reads/writes to certain addresses as requests for other actions, including interaction with other hardware on the card

No longer can you just throw something out there, no matter how stupid

Obviously this is not the context you're talking about, but I find this issue with brainstorming type sessions these days as well these days. Not just work sessions either, as another example, I'm on the advisory board for a local club, and the first meeting was really barren for quite a while.

It's gotten to the point that I always make sure to voice my philosophy early on - "not all ideas are good, but many good ideas start out as bad ideas and become good through conversation" - and proceed to throw a few incredibly stupid ideas to the group to break the ice. It seems to help.

Exactly this. I had COVID two years ago, the flu last year, and COVID again a couple months ago. Last year's flu was absolutely miserable; just as bad as COVID was the first time around.

I really don't want either one. Putting a piece of cloth on your face when you are/recently were sick really isn't much of a burden. I did.

Not solving all security issues isn't the same as not solving security issues. I'd rather my financial data be handled by software written in something that solves many whole classes of vulnerabilities than something that solves none of them.

I run Ceph in my lab. It's pretty heavy on CPU, but it works well as long as you're willing to spring for fast networking (at least 10Gb, ideally 40+) and at least a few nodes with 6+ disks each if you're using spinners. You can probably get away with far fewer disks per node if you're going all-SSD.