It depends on the exact situation. In this case there is coordination happening among multiple vendors who are working on various fixes in this space, which co

It depends on the exact situation. In this case there is coordination happening among multiple vendors who are working on various fixes in this space, which complicates things. Also complicated is that apart from "don't use Chrome" there's no useful mitigation users can do for this risk, and most Chrome users would never see any security-related blog post, nor act on it if they did. There are times when "screw you, I'm going public with this" is in fact the right thing to do. Again, in this particular case I don't think it is.