MOmochtar·Jun 6, 2022Submission
Bufbuild/connect-go: Simple, reliable, interoperable. A better gRPC
1 points · Open discussionbufbuild
connect-go
Go2022–2022
bufbuild / connect-go · Archived
connect-go
Moved to https://github.com/connectrpc/connect-go
2Distinct people
3Mentions
0Explicit recommenders
4GitHub stars
What to know before exploring
What it is
Moved to https://github.com/connectrpc/connect-go
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by 6-hour interval3 dated mentions
Observed mentions: 2022-06-02 02:43:41 UTC to 2022-06-06 06:30:12 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jun 2, 00:00 | 2022-06-02 00:00:00 UTC | 2022-06-02 06:00:00 UTC | 2 | 0 | 2 |
| Jun 2, 06:00 | 2022-06-02 06:00:00 UTC | 2022-06-02 12:00:00 UTC | 0 | 0 | 0 |
| Jun 2, 12:00 | 2022-06-02 12:00:00 UTC | 2022-06-02 18:00:00 UTC | 0 | 0 | 0 |
| Jun 2, 18:00 | 2022-06-02 18:00:00 UTC | 2022-06-03 00:00:00 UTC | 0 | 0 | 0 |
| Jun 3, 00:00 | 2022-06-03 00:00:00 UTC | 2022-06-03 06:00:00 UTC | 0 | 0 | 0 |
| Jun 3, 06:00 | 2022-06-03 06:00:00 UTC | 2022-06-03 12:00:00 UTC | 0 | 0 | 0 |
| Jun 3, 12:00 | 2022-06-03 12:00:00 UTC | 2022-06-03 18:00:00 UTC | 0 | 0 | 0 |
| Jun 3, 18:00 | 2022-06-03 18:00:00 UTC | 2022-06-04 00:00:00 UTC | 0 | 0 | 0 |
| Jun 4, 00:00 | 2022-06-04 00:00:00 UTC | 2022-06-04 06:00:00 UTC | 0 | 0 | 0 |
| Jun 4, 06:00 | 2022-06-04 06:00:00 UTC | 2022-06-04 12:00:00 UTC | 0 | 0 | 0 |
| Jun 4, 12:00 | 2022-06-04 12:00:00 UTC | 2022-06-04 18:00:00 UTC | 0 | 0 | 0 |
| Jun 4, 18:00 | 2022-06-04 18:00:00 UTC | 2022-06-05 00:00:00 UTC | 0 | 0 | 0 |
| Jun 5, 00:00 | 2022-06-05 00:00:00 UTC | 2022-06-05 06:00:00 UTC | 0 | 0 | 0 |
| Jun 5, 06:00 | 2022-06-05 06:00:00 UTC | 2022-06-05 12:00:00 UTC | 0 | 0 | 0 |
| Jun 5, 12:00 | 2022-06-05 12:00:00 UTC | 2022-06-05 18:00:00 UTC | 0 | 0 | 0 |
| Jun 5, 18:00 | 2022-06-05 18:00:00 UTC | 2022-06-06 00:00:00 UTC | 0 | 0 | 0 |
| Jun 6, 00:00 | 2022-06-06 00:00:00 UTC | 2022-06-06 06:00:00 UTC | 0 | 0 | 0 |
| Jun 6, 06:00 | 2022-06-06 06:00:00 UTC | 2022-06-06 12:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
3 sourcesI don't - I've never actually used flatbuffers. There are two pieces of code you'll want (if possible):
1. A `connect.Codec` implementation. I think it'd look almost the same as our Protobuf codec [0], but you'd use `FlatbuffersCodec.Marshal` and `FlatbuffersCodec.Unmarshal` (from github.com/google/flatbuffers/go). You _must_ have a `Codec`, but it looks like it should be pretty quick.
2. Ideally, you'd have a standalone program to parse your Flatbuffer schema and produce Connect code. The output would probably be very similar to `protoc-gen-connect-go`'s [1]. This isn't required, but it's a nice quality of life improvement (check out [1] to see the kind of conveniences it adds). With Protobuf, you'd do this via a `protoc` plugin and you wouldn't need to parse the schema yourself. From a quick look, I don't think `flatc` supports plugins
Read the rest
at all - so maybe you'd either skip this step or put in the effort to parse the schema yourself?
[0]: https://github.com/bufbuild/connect-go/blob/main/codec.go#L5...
[1]: https://github.com/bufbuild/connect-go/blob/main/internal/ge...
Also, thank you for making me stop and think about this in detail. I just pulled Flatbuffers out of a hat when I was writing that part of the docs and assumed that `flatc` supported plugins like `protoc`. Turns out that when you assume... I'm updating that portion of the documentation now :)
I’m tracking a similar issue in https://github.com/bufbuild/connect-go/issues/222 - is this roughly what you’re looking for?
In Connect: A Better gRPC