News for hackers. Stuff that matters.

mf192

Re:Protobuf Editions are here: don't panic on Thursday May 09, 2024 @08:18PM (#40314298)
Taking this a bit further, it's surprising how many companies sell API as a service but provide minimal support for that API, publishing like 1 client/sdk (and often not in the language you need, lol).

Just mindblowing that companies don't adopt a schema-first approach to appeal to a broader customer base. I've lost count of the number of hnd rolled clients I've had to write over the years.

It gets even better if the API itself is backed by some RPC framework. With that, users can simply generate a client and get going.

It feels like we can do better as an industry, this cracked me up because it's so true.

"a single JSON example as the only documentation is... unfortunate"

Ye, fwiw there is an example code size comparison here:

https://github.com/bufbuild/connect-web/blob/main/packages/c...

I'm sure someone will chime in on the implementation details, but hopefully others can give it a try with their projects!

Curious, do you see connect-web falling into the former or the latter group?
You're right, gRPC-web isn't there and likely won't get there. That's why we need something like connect-web.

- no proxies - smaller bundle size - idiomatic TS code in both runtime and generated code - streaming - ... and more

Re:A gentle-ish introduction to worst-case optimal joins on Wednesday June 01, 2022 @09:54PM (#31590413)
Well that escalated quickly, nice article!
Re:Connect: A Better gRPC on Wednesday June 01, 2022 @09:20PM (#31590208)
It always felt like gRPC was solving Google problems, heck that's (probably) what the g stands for.

Connect is for the rest of us. I wonder what kind of useful general-purpose interceptors folks will come up with?

Re:Connect: A Better gRPC on Wednesday June 01, 2022 @03:39PM (#31586916)
I think another differentiator is support for streaming. Tbh I am shocked at the number of folks that use streaming, but alas.

It was the #3 issue opened on twirp repository, but they never settled on a solution.

https://github.com/twitchtv/twirp/issues/3

One super underrated feature Connect offers for Go devs is access to the request/response headers. No more plumbing incoming/outgoing context :phew: