DRPC, a Replacement for gRPC
storj.io
DRPC, a Replacement for gRPC
1–3 of 3 posts
Re: DRPC, a Replacement for gRPC
#2> Where gRPC needs improvement: Let’s just get out here and say what not enough people are saying—in a nutshell, gRPC has feature creep, bloat and is trying to solve too many problems. It’s overcomplicated and has become a dumping ground of features, tangled in a standards body-based web of crap.
It sounds like they deemed more cost-effective to rewrite the protocol than learning how to use `grpc.Dial`
Re: DRPC, a Replacement for gRPC
#3> Where gRPC needs improvement: Let’s just get out here and say what not enough people are saying—in a nutshell, gRPC has feature creep, bloat and is trying to solve too many problems. It’s overcomplicated and has become a dumping ground of features, tangled in a standards body-based web of crap. It sounds like they deemed more cost-effective to rewrite the protocol than learning how to use `grpc.Dial`
I imagine they would need to know how to use the protocol in the first place if they're re-writing it, right? :)