Live data from Hacker News

Rust and the limits of swarm design

esr.ibiblio.org

51–55 of 55 posts

Re: Rust and the limits of swarm design

#51
My company has to approve all software on the development network. Getting newish versions of boost is bad enough. But keeping something like tokio or even simd and all its dependencies approved and in sync and then transferring them to the air gapped dev network is just this side of impossible. Is my company an outlier or is this common in bigcorp?

Re: Rust and the limits of swarm design

#53
post #33

Earlier quoted context omitted.

10 years is "that long", now?

How many libraries you use today that you already used ten years ago? Is there more than a handful?

I don't think it's about "libraries that you use". It's about the codebase of a widely used software. Most of the software I use existed 15 or even 30 years ago. It has been updated, of course, but not necessarily redesigned.

Re: Rust and the limits of swarm design

#54
post #25

Reminder that before you take anything ESR says remotely seriously, you should read http://www.catb.org/~esr/writings/dancing.html from beginning to end.

He's not a Christian, so we should ignore what he says about computers? That's preposterous.

That _really_ isn't a TL;DR; of that article.

Re: Rust and the limits of swarm design

#55
post #54

Earlier quoted context omitted.

He's not a Christian, so we should ignore what he says about computers? That's preposterous.

That _really_ isn't a TL;DR; of that article.

Haha nice try, but one won't be drawn into a theological debate about e.g. how many neopagan angels can dance on the head of an atheist pin. The point is that religious beliefs, no matter how banal or how fringe, are completely orthogonal to technical judgment. They are separate spheres. You've cannily left unclear the precise nature of the spiritual pablum you're peddling, but one can still see through your clumsy attempt to invoke religious prejudice.
Post reply on HN