everything should have an “i'm fucking around and i wanna find out” toggle.
languages, compilers, linters, IDEs, build systems - they are only tools. the person using the tools should have the final say.
anyway, “footgun culture” as i have now decided to call it, is why i love game modding and the communities surrounding it. modders don’t care if you commit atrocities in what used to be C, but one day transformed in its bed into an unholy macro language - they will pat you on the back and appreciate your innovative approach, then go back to committing crimes of their own.
“professional developers” could never even imagine such level of freedom. here i am, using my Microsoft-given right to assume the process module base always starts at 0x400000 and using raw pointers in my code, and no one can stop me
(somewhat related: i wish compilers had a better way of contextually managing warnings. usually the only options are “print all warnings”, “print a specific set of warnings that happens to be the least useful one”, and “provide an excel spreadsheet of warnings you want printed/ignored”. i’m tired of having to manually silence the tiny demon in my toolchain that condescendingly remarks “oopsie you can’t do this, you are leakeing memory! >:3”)