Re:Dear Google Cloud: Your Deprecation Policy Is Killing You
by jto1218 on Saturday August 15, 2020 @09:15AM
(#24168632)
that’s the whole point of the article though. Why should the “huge burden on the teams who maintain the stuff” be shifted to the customer who has less resources than Google to manage that burden. 12-15 months is not a long time. If you have to rebuild things that already work every year, you’re wasting a lot of time that could be spent building value for your customers.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You
by calcifer on Saturday August 15, 2020 @12:53PM
(#24170275)
> Having a 'support everything forever' approach is obviously going to impose a huge burden on the teams who maintain this stuff which is then going to limit the ability to make anything better
And yet AWS is doing just that while innovating at the same time.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You
by remus on Saturday August 15, 2020 @04:29PM
(#24172112)
AWS depreciate things too, though. For example https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-...
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You
by calcifer on Saturday August 15, 2020 @04:51PM
(#24172288)
Deprecate [1] doesn't mean remove though. While the old style paths are officially deprecated, they will be supported indefinitely. GCP's problem is that they deprecate and remove features.
[1] "Depreciate" is something else.
Personally, I think most of them seem quite sensible. Having a 'support everything forever' approach is obviously going to impose a huge burden on the teams who maintain this stuff which is then going to limit the ability to make anything better. The depreciation notices generally seem pretty good (12-15 months notice by the looks of it, sometimes followed by degraded functionality rather than complete removal of the feature).