> Twitter users

People. People are up in arms.

Anyway, yeah, that's insane. Even Google, who constantly shuts stuff down, usually does so with way more heads up. For comparison, Google Reader, a completely free service, shut down with 3.5 months advance notice. Google Wave got almost 6 months notice.

> Google Reader

It still hurts.

Since I missed on missing it, was there any particular feature that's not in other rss readers?

I have only user rss via gwene over nntp, if that went away, i'd miss it bunches.

It’s not about features. Nowadays, I’d go with a self-hosted Open Source application from the start. In fact, that’s what I am looking for at this very moment.

It was the day RSS died for me

I really don't get why this statement is so common. More or less every other hosted reader immediately offered a migration path, so getting out of Reader and up and running somewhere else was really easy.

I'm glad it happened, now I'm happier with Feedly than I was back then with Google Reader.

https://bazqux.com/ - Highly recommended. I'm a lifetime subscriber.

Let it live again with InoReader....

I do think that for commercial services like services in the Google cloud platform they give a year+.

All Google Cloud GA features will have at least 1 year of deprecation period.

7.2 Deprecation Policy. Google will announce if it intends to discontinue or make backwards incompatible changes to the Services specified at the URL in the next sentence. Google will use commercially reasonable efforts to continue to operate those Services versions and features identified at https://cloud.google.com/terms/deprecation without these changes for at least one year after that announcement, unless (as Google determines in its reasonable good faith judgment):

(i) required by law or third party relationship (including if there is a change in applicable law or relationship), or

(ii) doing so could create a security risk or substantial economic or material technical burden.

The above policy is the "Deprecation Policy."

Disclaimer I work for Google in Cloud.

Google does make a mess with consumer apps but it’s entirely different when it comes to Google Cloud or any of their enterprise products.

It certainly makes me rethink if docker services should be relied on in production.

Migrating off docker cloud will be a pain, but the service was already a pain to use, so maybe it's about time anyways.

But imagine being given 2 months to migrate off docker hub for image storage. Panic would ensue :)

I understand that having to abandon ship sucks, but wasn't the whole point of containers that they can be migrated easily? heck, the whole concept got its name from that idea. So why the fuss?

edit: typos

sure, but i'd wager that most of the pain point is getting orchestration tools to work on other platforms. and also vetting of other platforms, etc.

Because moving to another orchestration platform requires overhauling your CI/build system.

It's also due to the fact (which I also tweeted) that Kubernetes is not even supported on the stable release channel of Docker for Mac!

but why?

The whole point of containers is that they are ephemeral and can be booted up quickly anywhere because you statically link the whole fucking OS?

The APIs of platforms are often totally different. If you went to docker cloud for its simplicity and now have to move to AWS/GCP/Azure/etc. and don't have a dedicated DevOps that knows one of those platforms already, you have no choice other than taking a developer working on features and putting them on learning the new API in a few weeks including testing. ~8 weeks is not enough for that if you are a cash-strapped startup.

Such are the perils of using immature tools in your development chain and production systems.