its not always that simple. dropping in a new model is trivial, but highly specific workflows may rely on specific _invisible_ aspects of a model. when that model gets deprecated, the workflow needs to be rebuilt/re-tuned to work with a different model.

google's inability or unwillingness to provide stable timelines for model deprecation makes it risky to build complex workflows using their models

Load-bearing (whoops) quirks were noticeable months back, but haven't most flagship models become predictable and reliable?

100% agreed in the same boat right now. Feeling really screwed over by Google rn