Also, generally speaking, because the model is "library owner makes the LSCs," library consumers are happy to accept small/reasonable changes in API usage. Off

Also, generally speaking, because the model is "library owner makes the LSCs," library consumers are happy to accept small/reasonable changes in API usage. Off the top of my head I can only think of one time when an internal library deprecation caused a huge ruckus: some front-end framework was deprecated which led to a huge push to rewrite many of Google's internal websites. When I left even BigTable, MapReduce and other services are still supported even though they have been deprecated and their replacements (Spanner, Flume) had been GA for more than a decade. (Although their API calls may just go through a translation layer, not sure.)