[wokwokwok]

While this seems reasonable, surely there’s a caveat here:

If you have a successful popular product (firebase) and a not particularly successful or well loved product (GCP), does mixing A into B make sense?

It might make technical sense to have the robust engineering capabilities of B to support A.

…but if it’s driving customers away from A, because it’s starting to look like what they don’t like from B…

All I can say is that there seems to be a lot of pressure for GCP to succeed, and I’m pretty skeptical that the changes to firebase are being made for the sake of making that product better.

Betty had a bit of butter, but the butter was bitter, so she mixed the bitter butter with the better butter to make the bitter butter better but it made the better butter bitter…

[dcow]

I didn't realize people didn't like GCP. What’s wrong with it? It’s far creamier than AWS in my experience.

[js4ever]

It's from Google, they deprecate things every 6 months including APIs your app is using, if you don't follow your app will be down pretty quickly. AWS nearly never do breaking changes.

[darzu]

AWS GameSparks. Being shut down end of November and bringing down one of my favorite games with it, because the devs were foolish enough to believe what you believe, that AWS sticks with its products.

[sofixa]

It's AWS page says Preview, meaning it has never gotten to an official stable release. It's like using a beta/rc product, there is an explicit warning this is not the final version and it might not get anywhere.

[opyate]

Please provide a source. My internet sleuthing is failing me at the moment.

[darzu]

https://liquidbit.com/killer-queen-black-update%EF%BF%BC/

Killer Queen Black is shutting down due to GameSpark being sunsetted. The game was released 2019.

[netheril96]

But since Firebase is from Google now, anyone who worries about Google deprecating products have equal worries whether Firebase is based on GCP or not.

[wodenokoto]

I think it’s a HN bubble thing.

Outside of HN, I find developers (at least in Europe) often prefer GCP and businesses have full faith in the offering because of the Google stamp.

For Azure I have yet to find a developer who likes it, but businesses are drawn to it due to the packaging with other Microsoft services (eg you buy office 364, teams, Active Directory and Azure together in a Enterprise package) and businesses have full faith in the Microsoft stamp of approval.

[sofixa]

Same, of all the people I've interacted with, it's AWS and GCP which are liked (AWS mostly for features, GCP more for UX/DX), Azure is at best accepted and the only reasons anyone uses are "we were already a MS partner/shop".

[pjmlp]

On my corporate world bubble in Europe, it is usually either AWS or Azure, nothing else comes into the picture unless required by the customer.

Maybe the fact that we are a Java/.NET shop has some influence on it as well.

[michaelcampbell]

The more I ponder this post, the more it rings true with my experience. Insightful.

[canadianfella]

> If you have a successful popular product (firebase) and a not particularly successful or well loved product (GCP), does mixing A into B make sense?

Firebase is more successful than GCP? In what way?

> Betty had a bit of butter, but the butter was bitter, so she mixed the bitter butter with the better butter to make the bitter butter better but it made the better butter bitter…

?

[nvrspyx]

GCP is the bitter butter and Firebase is the better butter. Mixing GCP with Firebase is making Firebase worse.

At least, that's how I understood the nursery rhyme in the context of the parent comment.

[flutas]

> > Betty had a bit of butter, but the butter was bitter, so she mixed the bitter butter with the better butter to make the bitter butter better but it made the better butter bitter…

> ?

They are saying that taking a good thing and combining it with a bad thing, doesn't make the bad thing good. It makes the good thing bad.

I have no "dog in this fight" (side note, any better phrases to use there?) but just explaining what they tried to convey.