2 ms·

I think the commenter was saying google squandered its lead ("goodwill" is how I would refer to it) in providing open and interoperable services, not the more r

I think the commenter was saying google squandered its lead ("goodwill" is how I would refer to it) in providing open and interoperable services, not the more recent lead it squandered in AI. I agree with your point that they've made up a lot of that ground with gemini 2.5.

simonw 1y ago
Yeah you're right, I should have read their comment more closely. Google's API's have a way steeper learning curve than is necessary. So many of their APIs depend on complex client libraries or technologies like GRPC that aren't used much outside of Google. Their permission model is diabolically complex to figure out too - same vibes as AWS, Google even used the same IAM acronym.
- Aeolun 1y ago
  I feel like the AWS model isn’t all that hard for most of their API’s. It’s just something you don’t really want to think about.
- PantaloonFlames 1y ago
  > So many of their APIs depend on complex client libraries or technologies like GRPC that aren't used much outside of Google. I don't see that dependency. With ANY of the APIs. They're all documented. I invoke them directly from within emacs . OR you can curl them. I almost never use the wrapper libraries. I agree with your point that the client libraries are large and complicated, for my tastes. But there's no inherent dependency of the API on the library. The dependency arrow points the other direction. The libraries are optional; and in my experience, you can find 3p libraries that are thinner and more targeted if you like.
- paul-tharun 1y ago
  I sometimes feel the complexity is present by design to increase the switching cost. Once you understand it and set it up on a project, you are locked in, as the perceived cost of moving is too high.
- xyzzy_plugh 1y ago
  This is bizarre to read. gRPC is used _widely_ outside Google. I'm not aware of any API that requires you to use gRPC. I've never found their permission model to be complicated at all, at least compared to AWS.

simonw 1y ago

Yeah you're right, I should have read their comment more closely. Google's API's have a way steeper learning curve than is necessary. So many of their APIs depend on complex client libraries or technologies like GRPC that aren't used much outside of Google. Their permission model is diabolically complex to figure out too - same vibes as AWS, Google even used the same IAM acronym.

Aeolun 1y ago
I feel like the AWS model isn’t all that hard for most of their API’s. It’s just something you don’t really want to think about.
PantaloonFlames 1y ago
> So many of their APIs depend on complex client libraries or technologies like GRPC that aren't used much outside of Google. I don't see that dependency. With ANY of the APIs. They're all documented. I invoke them directly from within emacs . OR you can curl them. I almost never use the wrapper libraries. I agree with your point that the client libraries are large and complicated, for my tastes. But there's no inherent dependency of the API on the library. The dependency arrow points the other direction. The libraries are optional; and in my experience, you can find 3p libraries that are thinner and more targeted if you like.
paul-tharun 1y ago
I sometimes feel the complexity is present by design to increase the switching cost. Once you understand it and set it up on a project, you are locked in, as the perceived cost of moving is too high.
xyzzy_plugh 1y ago
This is bizarre to read. gRPC is used _widely_ outside Google. I'm not aware of any API that requires you to use gRPC. I've never found their permission model to be complicated at all, at least compared to AWS.