Love too see the same people that have no problem copy-pasting my code without attribution, also try and descredit my other work.
-
-
I bet these people will follow up on this claiming they're the true victims here. Oppressed by the evil tyranny of Rust's working groups. While in reality we've tried engaging countless times, but they're simply not interested. Like: this has been *years*, even before I was part
Show this thread -
These people? Ya. I'm tired. Sorry. This has been going on for months. And like, I just can't. At some point I was keeping a diary in which ways they were being abusive. I was noticing it was too much to remember, and had to write it down. Ugh.
Show this thread -
Anyway. I've got zero hopes we'll ever successfully collaborate on anything. It's sad, but whatever. All I want is to be able to work on things peacefully. To peacefully coexist; trying out stuff from different angles. But yeah that feeling is apparently not shared.
Show this thread -
I know I'm supposed to keep my composure on this stuff because I'm "represent the Rust project". But I just can't keep all this stuff in anymore. It feels like I have to walk on eggshells with *everything* around async Rust.
Show this thread -
Every single project I make is overshadowed with a fear of retribution. In my 5 years with Node I don't think I've ever worked on anything in private. With async Rust everything I work on has to be private, out of fear of getting smeared before I even get started. It sucks a lot
Show this thread -
It's only when I think I've proven an idea to be good, usually after weeks or months of iteration, that I publish it. Like. This is not healthy. This is not good. And it shouldn't be that this is the only way that I feel comfortable working. But I know it's not my fault.
Show this thread -
Thank you for speaking out publicly Aaron. I know it isn't easy, but I'm glad you've decided to
https://twitter.com/aaron_turon/status/1145074057508843520 …Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.