Finally someone who gets it. The echo chambers that exists among programmers today is painful. And it is especially bad on SO when you ask a question and someone just comments one of the following without going into depth as to the why:
"Don't use goto it is bad"
"Don't use reflection it is slow"
"Don't do that it is an anti-pattern"
"Don't use X it is considered bad practice"
I understand there are rules of thumb when programming, but they are not set in stone. There is a reason the language designers haven't removed or deprecated features.
i was talking to a friend about this the other day, it makes working with other people infuriating, doubly so if you work in the microsoft .net world.
people don't just avoid but they actively oppose thinking for themselves. if it isn't a "principle" or a "rule" then it's wrong, and if there isn't a popular blog post granting you permission to do something, it's probably a bad idea.
you can take an idea, walk them though it, lay out the pros and cons, explain how it helps to solve a problem, even create a working prototype and show it to them, and the entire microsoft-brained team will watch it work then start groaning "hmmmmm, ehhhhhhhh, uhhhhhhh" in unison before deciding that they'd rather not solve the problem at all than do something "scary".
Some of us use goto in C# because it has none of the footguns, even if it annoys some less open-minded colleagues :)
I do feel you regarding the culture (arguably, it’s a thing with many modern languages sadly) which is why I’m taking a year-long vacation to work on OSS projects - the language is beautiful but the atmosphere was insufferable in the last team. There are better places fortunately but one needs to recharge.
"Don't use goto it is bad"
"Don't use reflection it is slow"
"Don't do that it is an anti-pattern"
"Don't use X it is considered bad practice"
I understand there are rules of thumb when programming, but they are not set in stone. There is a reason the language designers haven't removed or deprecated features.