3 ms·
For 99% of users it should not make a difference. The link you included shows that protobufs are at least 15% better for all users, and as much as 57% better f
by onion2k 4y ago
For 99% of users it should not make a difference.
The link you included shows that protobufs are at least 15% better for all users, and as much as 57% better for cases where the data is small. Doesn't that mean for 100% of users it will actually make a difference?
Your users might not care about the difference but it will be there.
- arein3 4y agoUsually when visiting a website, saving a few kilobytes on the client side on requests to backend does not make any difference.
- billions 4y agoAgreed. ProtoBufs slows code iteration velocity tremendously. Saving 100 milliseconds on page load while reducing developer efficiency by 30% = a net worse product for end users.
- jameshart 4y agoA feature that never ships has value for 0% of users. Actually realizing that speed up for your users will take time away from delivering features. Engineering is a trade off, always will be.
- thdespou 4y agoHaha awesome response.
- jtolmar 4y agoYou'd also have to compare this against the download size of the protobuf library itself.
- marcosdumay 4y ago> 57% better for cases where the data is small You don't optimize things for the cases when they are fast. (Unless the gain is a couple of orders of magnitude; certainly not for a 50% speedup.) The 15% gain is the one that matters. On practice, it comes at the expense of a more complex (thus larger, negating some of it) and less reliable system. It is very rare that this trade-off is worth it.
- deleted 4y ago[deleted]