3 ms·
Download size is a "tragedy of the commons" situation. The overall size usually isn't owned by anyone and each contribution to increasing the size is usually sm
by xenadu02 5y ago
Download size is a "tragedy of the commons" situation. The overall size usually isn't owned by anyone and each contribution to increasing the size is usually small so monitoring it daily or weekly doesn't help. It is only when you are able to compare the size 1 month, 6 months, 12 months ago that a large jump can be observed - one accomplished by lots of tiny 0.1% increments.
But even if you do notice that and file bugs what team in their right mind would spend time trying to reduce their own component's size by 2% when they could spend that time on features or bug fixing instead? And if you asked the majority of their users would agree - "F'k the 20MB, fix bug XYZ/finally implement feature ABC".
Despite each individual decision along the way being arguably the correct decision the product still adds up to +30% every year.
- rrrrrrrrrrrryan 5y ago"Never do any download size optimizations" is just as silly as "shave off 20MB at the expense of implementing a much-needed feature." Usually there's some ultra low-hanging fruit that everyone knows about, and if download size has become an issue, a bit of time should absolutely be allocated to basic housekeeping tasks as long as the product is supported.