bufbuild

5 ms·

1.
by bufbuild 1mo ago
Totally, and we appreciate the sentiment. But the title was meant to be lighthearted, and instead it clearly struck a nerve. That's not our intent, and it was easy to change, so we just swallowed our pride. We rather the conversation b
2.
by bufbuild 1mo ago
We're terrible comedians - we've added something of a mea culpa to the post!
3.
by bufbuild 1mo ago
Fair enough - feedback taken, we don't have a second career in comedy! Appreciate the feedback - we're renaming the post once GitHub is back online, and are adding the following to it for transparency: > Edit: In full transpare
4.
by bufbuild 3mo ago
> No clear and easy way to use it with HTTP/1.1. Neither is specific to Python. > It seems like Google focused on gRPC, but the real prize for adoption would've been going after the simple HTTP+JSON use cases. Like an offici
5.
Show HN: CEL by Example(celbyexample.com)
84 points by bufbuild 7mo ago|40 comments
6.
Oneofs are a disaster. Protovalidate has fixed them(buf.build)
1 points by bufbuild 1y ago|0 comments
7.
Never Use Required(buf.build)
2 points by bufbuild 1y ago|0 comments
8.
by bufbuild 2y ago
Connect libraries are 100% compatible with gRPC - in many cases, they implement the gRPC spec more faithfully than the core libraries themselves: https://buf.build/blog/grpc-conformance-deep-dive TLDR: there should be
9.
by bufbuild 4y ago
It's worth checking out our take on a lot of these problems: https://buf.build/blog/connect-web-protobuf-grpc-in-the-brow...
10.
by bufbuild 4y ago
protobuf-es does as well! https://github.com/bufbuild/connect-web
11.
by bufbuild 4y ago
That is for the text format, which is a serialized representation of Protobuf data. As they specify in the linked doc, it is not the format for the actual language: > This format is distinct from the format of text within a .proto schema
12.
by bufbuild 4y ago
Of course, also check out Connect :-) https://connect.build
13.
by bufbuild 4y ago
The URI is per-RPC, specifically at /service/method, if that helps. On cacheability, do check out https://connect.build/docs/protocol#future-extensions - it’s something we continue to put thought into to make
14.
by bufbuild 4y ago
And there’s Buf Studio :-) https://buf.build/blog/buf-studio https://studio.buf.build
15.
by bufbuild 4y ago
We’d really recommend checking out the Connect protocol in this case - we totally understand that a new custom protocol would induce a few eye rolls, but it’s about as simple as it gets, especially with unary - it’s just HTTP POST at &#x2
16.
by bufbuild 4y ago
It already does! The connect protocol supports all streaming mechanisms. The beauty of the Connect ecosystem is that no proxies are required - the Connect protocol works just as well from the browser as it does on the backend.
17.
Introducing buf format(buf.build)
1 points by bufbuild 4y ago|0 comments
18.
The Buf Schema Registry, a dependency management system for Protocol Buffers(buf.build)
11 points by bufbuild 5y ago|3 comments
19.
Document Your APIs and Increase Your Developer Productivity(buf.build)
5 points by bufbuild 5y ago|0 comments
20.
Maintaining a Stable Protobuf API(authzed.com)
18 points by bufbuild 5y ago|1 comments
21.
GitHub Actions for Buf now available(blog.buf.build)
5 points by bufbuild 5y ago|0 comments