I'm not sure what you mean by cherry-picking, I'm directly addressing their comment. The kinds of struggles `xrd` mentions (Gatekeeper, protocol handlers) are n

I'm not sure what you mean by cherry-picking, I'm directly addressing their comment. The kinds of struggles `xrd` mentions (Gatekeeper, protocol handlers) are not library level dependencies, they are the platform their code is running on. Comparing that to a js library is just the wrong equivalence. If their beef was with AppKit, or NSWindow or something at the dependency level then yeah it's fair to compare that to an npm package. The bulk of my experience has been with native development, so I find these struggles familiar and un-threatening. However, when I do browser-based development and I'm faced with one of those massive "Browser compatibility" tables on Mozilla.org explaining how this "standard" is implemented in wildly different ways across the major browsers, and then the reality turns out to be different from what the table suggested, I get as frustrated as `xrd` is.