|
Top-level
 If my component was 1) very complicated, needing to handle lots of different state then I would absolutely use this well-tested, widely-used library. It would be worth the cost in both added external dependency and file size. But the library gets 1 million downloads a week and I bet most of those are use cases where this is sheer overkill. 5 comments
@muffinista I checked it's not -- it's really about providing toggleable features for lots of different UX edge cases  @darius yeah that's a bummer. i had a similar issue lately with toast/notification libraries. they're all huge! i wrote one that's ~30 lines of css and js  @darius a lot of people i’ve worked with truly only see cost in one way: how long will it take to implement this feature it is misery i’m glad you’re considering this stuff! if only bc it heartens me to know all projects aren’t equally myopic @mood haha yeah. I mean I am reimplementing old code from the ground up so the N hours of implementation time that this library saved the devs 2 years ago is turning into ~4N now. (And yeah I get that sometimes you need to ship something NOW and sometimes that means you download a thing that does the thing. But also this particular component could have been made in... idk ~3 hours?) |
Gregory's Server
@darius i wonder if it's for backwards compatibility with older browsers but more likely it's just bloat