8 ms·

> The cumulative loss of something can be huge, but still don't matter because its distributed to a degree where it is barely a rounding error. Are you claimin

> The cumulative loss of something can be huge, but still don't matter because its distributed to a degree where it is barely a rounding error. Are you claiming it doesn't matter to anyone or just you? > If I give you back 5 seconds each day, will it matter to you? Will you be able to enjoy or do something that you otherwise wouldn't? I'd welcome the time back since I don't lose anything in return anyway. So, a big YES here. Generally I would put faster library as a plus. Working in a big company, when choosing between 2 open sources, we will need to list down pros and cons. Among other things, being 4x smaller is definitely one of the plus consideration. I try not to exaggerate this; it's not a major plus, but a plus nonetheless Saying these doesn't matter is disingenuous. To you, maybe, but not for most. If everything else is equal, you would choose chalk despite it is 4x bigger in size and slower? Most will choose the smaller and faster library.

samastur 5y ago
Yes, I am claiming that saving 5 seconds out of 86400 in a day does not matter to any healthy person. As a web developer I generally prefer things being faster and/or smaller too, but I would not change a working field-tested library for negligible effect. The problem in the case that is being discussed is not which library would be chosen when none is being used yet, but does it make sense to replace an existing one to save 90K of disk space and maybe a few seconds per day? To me this looks like very definition of bike-shedding and yes, I would definitely not switch library if these are the only compelling reasons. 4x smaller than the other one doesn't really tell anything without considering how big the whole app that uses this library is. On our fairly basic Nuxt project node_modules directory takes 250M. Do you really think any of us should care about 90K? And lastly, you don't know me. Save your "disingenuous" remarks for people you do.

samastur 5y ago

Yes, I am claiming that saving 5 seconds out of 86400 in a day does not matter to any healthy person. As a web developer I generally prefer things being faster and/or smaller too, but I would not change a working field-tested library for negligible effect. The problem in the case that is being discussed is not which library would be chosen when none is being used yet, but does it make sense to replace an existing one to save 90K of disk space and maybe a few seconds per day? To me this looks like very definition of bike-shedding and yes, I would definitely not switch library if these are the only compelling reasons. 4x smaller than the other one doesn't really tell anything without considering how big the whole app that uses this library is. On our fairly basic Nuxt project node_modules directory takes 250M. Do you really think any of us should care about 90K? And lastly, you don't know me. Save your "disingenuous" remarks for people you do.