Even in bridge mode you can still be slowed down by the modem if its CPU can’t handle your traffic. That’s unless the isp modem offer a complete passthrough. That’s what was happening to me even in bridge mode where I was getting my own IP through pppoe. The modem couldn’t be made into full passthrough and was hitting 100% CPU.
Bridge mode still means you go through their hardware. I had issues with my ISP modem because even if it was in bridge mode I was basically ddos-ing it with my usage.
In the end I got an sfp module that mimick being the modem and plugged the ISP fiber right into my opnsense box where the CPU was plenty.
I say ess cue ell for the sake of uniformity because it’s not Mysequel nor Postgresequel and the language changed from Sequel to the acronym SQL in the 70s so not really in the “too new” ballpark anymore.
There’s nothing limiting what a comment should be as far as I know.
As an example of what I mean, I’ve seen in a 10k+ lines python code a few lines of bit manipulation. There was a comment explaining what those lines did and why. They didn’t expect everyone to be proficient in bit manipulation but it made it so that anyone could understand anyway.
IMHO the issue in this situation is not the comment but that the person updating the code didn’t do his job properly which shouldn’t be an excuse not to do it from the start.
I don’t care how much you think your code is readable, plain text comments are readable by everyone no matter the proficiency in the programming language used. That alone can make a huge difference when you’re just trying to understand how someone handled a situation.