In the software industry we run into absolute statements like that all the time.
- Thou shalt not have code in your code-behind.
- Thou shalt not new up objects in code (IOC only, please!)
In most cases, those are 1. reactionary due to proliferation of bad practices by n00bs, and 2. based on passed-down “wisdom” which has not been questioned by people passing it on. What starts are guidance with qualifiers/criteria becomes mantra and then religion.
I always treat them with a grain of salt.
If you understand the reasons why those rules are there, and then with that education, decide they aren’t appropriate in this situation, you’re doing the right thing. If you tell people “you should never do X” like in that post, you’re wrong.
This is actually a bit of a hot button of mine when it comes to software. It’s often used as a way for experienced to assert some superiority over new folks. I’m not saying you’re doing that here (seriously), but it is something I tend to speak out against. The person you quoted is doing exactly that, though. He (or she) telling people “never” and then being really iffy about the reasons why, is a classic example of the rules being passwed down without any understanding of the real reasons.
In my case, a straight line is the shortest distance between two points, and it avoids the no-trace area around the mounting holes. I could add a via and route it on the back of the board but then I cut up the ground plane more. In my case, I decided this was the most appropriate approach.