3 ms·
This amazes me with just how bloated and inefficient simple things have become. In ~4 decades we went from literal 'netcat chat' where your message may be shor
by userbinator 4y ago
This amazes me with just how bloated and inefficient simple things have become.
In ~4 decades we went from literal 'netcat chat' where your message may be shorter than TCP/IP headers most of the time, to slightly more featureful but still simple with IRC, and then the IM protocols of the 90s/2000s with even more features but usually quite tame (speaking from experience of working with MSNP). After that it started getting worse with XMLification, and now the web-based stuff.
But those last two requests aren’t API requests, they’re just requests to fetch images!
...that naturally raises the question of "what images? I didn't send any."
It's horrifying to see a <40B message get turned into 730B. I suspect that the majority of the time, the actual message content you send will be dwarfed by overhead.
- intelVISA 4y ago40B message transmuted into 730B of meta-data gold. Pretty good ROI! If it's free you're the product (et cetera)
- xuhu 4y agoMessenger conversations are persistent, so a more apples to apples comparison would be against emails.
- andirk 4y agoI was building a Google Analytics looking admin interface for a company and I kept glancing over at GA requests/responses for guidance. It would send a ton of redundant data over for each 'next' table rows like the column headings and some styling stuff. It wasn't ugly but it was way heavier than needed. So I did similar and it worked great. Update: Looking at the mostly unusable GA4, their 'next' table row responses are much more concise. The only problem now is that entire application is a pile.