@sima @karolherbst @cas @kernellogger @airlied

Sorry for the stupid question, but what harm did Marcan's posts outside the mailing list actually do? I find lkml threads difficult to navigate and I don't know off-hand who is or is not a common participant, but I couldn't see many drive-by responses in the thread itself; were there a bunch that I missed? Or was it just drama outside the mailing list, and if so, why does that matter?

@pluralistic you say that we haven't "added the federation systems that would enable freedom of exit to its service". we have done that. what I think you *really* want is a peer running actual competitive alternatives for each component. That is similar, but different!

If it is possibly, why isn't anybody doing it? That is a great question! we have theories, and have done a lot already to encourage it (open code, open protocol, docs, etc)

@iximeow @jyn @rain yeah you can write the equivalent of async rust in c++ with no borrow checker. it is so dubious that there's a clang tidy lint just telling you to not capture *anything* in an async lambda *ever* because the *lambda object itself* can and often will vanish before the end of its own execution due to the surrounding function returning.

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rcoro-capture

it's simply absurd.