I wonder how feasible it really is to do a small app backend with something a tiny bit more efficient than REST. It’s weird that the most inefficient form of transmitting data on the Internet became the most common way to do it. But at least earlier the generated Protobuf code was absolutely hideous and inefficient outside the raw wire protocol with classes that were total ass to use. But it seems to be the best we have so far?
https://imgflip.com/i/98ug9t
[#]protobuf
=> More informations about this toot | More toots from chakie@toot.community
@chakie
If the client and server can minimally use gzip, JSON over REST (or just as API endpoints) compresses very well with most data. It’s good enough that I couldn’t justify in a recent project spending time messing with binary formats like protobuf.
Part of me was disappointed as I wanted to do more exploring, but I’m glad I didn’t add the extra complexity of protobuf (or similar).
[#]WebDev
=> More informations about this toot | More toots from wiredprairie@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini