A well-documented config file is like the exact opposite of “tech paternalism”.

Windows users are used to everything being so locked down that it’s virtually impossible to mess up your system… lots of this stuff is in config files because exposing it for everyday users would be asking for people to completely brick their workflow.

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.

Motherfuckers are actually arguing that seeding a torrent isn’t “distributing” unless they can show an instance of someone downloading a book from their IP… If that flies they better overturn every fucking piracy conviction ever.

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”…

Your reading comprehension is shit.