I don’t know, I’d call that comment dismissive and unhelpful so he was justified in biting back.
how is asking a question dismissive?
Stack timer is useful, but as we all know, scrubber duration is based on quantity of CO2 absorbed. It can take 20 minutes, or 20 days, it may be 18 minutes or 18 days if it's cold. The computer doesn't know any of that so they just count down a timer that you arbitrarily set based on your knowledge of the scrubber. If you are doing extended prebreathes, then factor that into the timer.
I pointed out an issue with his suggestion for starting the timer when .19 is turned off. I said that because you may prebreathe on .19, you may just not turn it off. If
@Shearwater is going to implement a change to their computers, it has to be something that isn't going to cause them a liability issue. Having it set the way they have it now is fairly idiot proof. If the computer is on, we count. If the rebreather is diving, we count. The real important part is the dive, and unless you do a truly extensive prebreathe at the surface, you aren't going to have anything significant to worry about. The suggestion of turning off .19 means that you could go an entire dive without the stack timer ticking down and that brings on risk.
If there is a way to implement it that doesn't remove the computers ability to auto-start for the important part, then it may be worthwhile. I.e. his suggestion could work provided there is an auto start as soon as the sensors detect depth, or even if there was an option to manually start the stack timer ahead of the "dive" mode, but I wouldn't implement a third option without some sort of override.
The unintended consequences of a "mode" need to be taken into account during evaluation of suggestions and that is what I was pointing out.