[andreif]

I thought you meant API and parameters. Blaming them for product names is weird to me.

[jgalt212]

It's nice when things do what they say on the tin. That being said, it's hard to build a "brand" when you start out with a generic name.

[andreif]

How many popular products have you named and launched? Naming products is hard to meet both usability and marketing objectives. This has never been as big of a problem for me, as GCPs APIs for example. Those are the true evil. Product names I care little for.

[arccy]

aws api and param names are stupidly long CamelCased and not even consistent half the time like a leaky abstraction over their underlying implementation

[andreif]

You remember any example? I don't call API directly and usually use CLI/SDK/CDK that work a lot better than gcloud. I did see some inconsistencies between services (e.g. updating params for SQS and SNS) and that could definitely be improved. But honestly, comparing to GCP mess, AWS is ten times better.

[geraldhh]

why is that?

[andreif]

Why it's weird to blame them for product names? Because their purpose slightly different. I can see where negativity comes from and understand, but product name is a lot less important as consistent API experience. AWS is the best among big players by far, hats off and well-done to their teams and leadership. I hope the others will finally learn and follow.