News for hackers. Stuff that matters.
Re:A four year plan for async Rust by insanitybit on Tuesday November 07, 2023 @12:21PM (#38179733)
The way I see their comment, and they'll have to forgive me if I'm wrong, is that the "async is bad" posts are generally not great.

a) They often focus on problems that, at least for me (and many others) are not significant. For example, acting like writing "+ Send + Sync + 'static" is causing your hands to seize in pain. Or they ignore that you can "block_on" a future.

b) They're then often interpreted by people who have very little context on async or rust at all. Look at the initial comment of "Async is a wart", it's idiotic. Look at how stupid the comments section is, how people are not talking about literally anything that boats wrote.

c) They make propositions that aren't very helpful. They mostly say "it was a mistake!" or "we don't need multithreading" or "we want TPC".

Contrast with Boats' post, which is far more contextual, far more historical, and proposes actual solutions and future work to be done.

It's quite frustrating to see the same sorts of complaints over and over again, especially when they're often not super great complaints to begin with.

Re:A four year plan for async Rust by CyberDildonics on Tuesday November 07, 2023 @12:34PM (#38179949)
I don't think that's what they are saying, I think that's what you're saying. I would be frustrated by that too, but I don't see any of that here.
Re:A four year plan for async Rust by insanitybit on Tuesday November 07, 2023 @12:37PM (#38179987)
Well they're responding to someone saying "Async is a wart".