2 comments

  • agentik4 minutes ago
    <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=48126889">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=48126889</a> just posted a thread, for a compeletly unrelated AIP definition :)
  • cbarrick29 minutes ago
    This is a fork of Google&#x27;s AIPs (API Improvement Proposals) [1], which is the standard for all of Google&#x27;s public APIs.<p>More context at [2].<p>[1]: <a href="https:&#x2F;&#x2F;aip.dev" rel="nofollow">https:&#x2F;&#x2F;aip.dev</a> [2]: <a href="https:&#x2F;&#x2F;aep.dev&#x2F;blog&#x2F;history-of-aeps&#x2F;" rel="nofollow">https:&#x2F;&#x2F;aep.dev&#x2F;blog&#x2F;history-of-aeps&#x2F;</a>
    • ventana0 minutes ago
      &gt; which is the standard for all of Google&#x27;s public APIs<p>Far from that, unfortunately. A lot of Google public APIs predate AIPs and it&#x27;s practically impossible to fix them and make them compliant. Possibly the worst offender is the Compute Engine API [1], which, to the best of my knowledge, is REST only (no gRPC), uses its own conventions related to page size &#x2F; next page token, and, in general, is special in many ways. One of the ways it&#x27;s special is it&#x27;s size: its definition in Google&#x27;s own Discovery format [2] is a 6MB JSON.<p>It&#x27;s an extremely difficult problem to standardize multiple APIs produced by multiple teams, and then keep the changes compliant. Google did a great job, but it&#x27;s still very far from the perfect state.<p>[1]: <a href="https:&#x2F;&#x2F;docs.cloud.google.com&#x2F;compute&#x2F;docs&#x2F;reference&#x2F;rest&#x2F;v1" rel="nofollow">https:&#x2F;&#x2F;docs.cloud.google.com&#x2F;compute&#x2F;docs&#x2F;reference&#x2F;rest&#x2F;v1</a> [2]: <a href="https:&#x2F;&#x2F;www.googleapis.com&#x2F;discovery&#x2F;v1&#x2F;apis&#x2F;compute&#x2F;v1&#x2F;rest" rel="nofollow">https:&#x2F;&#x2F;www.googleapis.com&#x2F;discovery&#x2F;v1&#x2F;apis&#x2F;compute&#x2F;v1&#x2F;rest</a> - warning: 6 megabytes JSON