863 karma · joined January 9, 2021
Regardless, this isn't what I was referring to by leaks upthread.
(Oh wait, yes they were.)
> He said that he would spend the bulk of the talk on moving away from TCP, but that there is also a need for a lighter-weight remote-procedure-call (RPC) framework. Beyond that, he believes that it no longer makes sense to implement transport protocols in software, so those will need to eventually move into the network interface cards (NICs), which will require major changes to NIC architectures as well.
So basically hardware-accelerated RPCs. I can get behind that in theory, but encoding RPC semantics in hardware sounds like a recipe for extremely slow evolution and very limited hardware choice.
Independent of that: what crosses the line is nowhere like settled. Many people like to act as if what they find offensive must obviously be treated as if it were beyond the pale. They're probably living in a small filter bubble where the speech in question is unquestionably offensive. Their views are rarely majority opinions, however.
I think the only thing I can say wrt poorly/expertly written is I haven't met very many people capable of writing top-quality Rust (most are "I've used it for a side project or two"), whereas my professional network is filled with C experts.
I expect this is due to the types of jobs I work, but the point stands: if we were to try to replace C with Rust we would likely get at most "journeyman" quality.
When replacing battle-tested code with newly-written code, you're going to encounter new bugs. Guaranteed.