>It’s that they push out new products, encourage communities to use them to make “amazing” things, and then don’t support them well over the long term. They let cool projects atrophy and die.
This is the absolute root of the problem, and one that is unique to Google among the big cloud providers. Yes, AWS may roll out new features, but generally the core stuff stays put.
I'm not losing sleep over route 53 getting "sunset" with a 1 month notice. Can't say the same about Google. While it won't sink them, I can see this becoming a bigger and bigger obstacle as the number of IT pros who get caught in the fallout of Google's internal ADHD grows.
If Google, or a vendor using a product on top of Google services contacts me, I'm not touching it unless they're willing to enter into an SLA where they pay for the trouble of migrating my stuff when they axe the service.
In other words, I'm not using it, because no one would ever offer such a thing.
This is the absolute root of the problem, and one that is unique to Google among the big cloud providers. Yes, AWS may roll out new features, but generally the core stuff stays put.
I'm not losing sleep over route 53 getting "sunset" with a 1 month notice. Can't say the same about Google. While it won't sink them, I can see this becoming a bigger and bigger obstacle as the number of IT pros who get caught in the fallout of Google's internal ADHD grows.
If Google, or a vendor using a product on top of Google services contacts me, I'm not touching it unless they're willing to enter into an SLA where they pay for the trouble of migrating my stuff when they axe the service.
In other words, I'm not using it, because no one would ever offer such a thing.