

Yeah you’d think that if you never played before it ruined the entire game.
Yeah you’d think that if you never played before it ruined the entire game.
Most players are using casual mode which is terrible. The community servers in TF2 are a pale shadow of what they once were.
Sure, I don’t think it’s like toxic or anything, but I also understand why Martin viewed the situation as an impasse requiring a decision from on high. Also, from my limited understanding it sounds like the new code was in a sequestered rust-only section of the dma subsystem, so I’m not clear on exactly what new burdens were being placed on the C dma maintainers.
If you read the article, the main issue is not the fact that it’s Rust itself, but that it’s a second language entering the codebase. There’s definitely some validity to the argument.
My personal view is that any C developer who doesn’t want to learn Rust is going to kick themselves once they do.
To be fair, I’m not sure how “I will do everything in my power to oppose this” is the anti-Rust side “work[ing] towards some resolution”…
I’m a Valve stan but it’s disgusting how they’ve abused and neglected TF2. It would unironically be significantly better if they just rolled back every change since 2016.