I went and looked at the source, and while I find it hard to follow, it&#x27;s clearly not just implementing the 10-30 line function you&#x27;re hoping for. It&#x27;s doing lots of other things.<p>An enormous portion of that code lives under static-module, which appears to do some kind of bundling&#x2F;codegen&#x2F;code swapping logic. So it depends on a parsing library for JavaScript.<p>I don&#x27;t know if this is a good design, I don&#x27;t follow the exact functions of this library, but I&#x27;m completely unimpressed by you having a drive-by reaction of &quot;4 megs for this library?&quot; It feels like you just scanned the library and decided it was wrong, without asking what it was trying to do.<p>In the same vein, what I want to see from this discussion is people delving into specifics. The original article did that a little, but I want to know more. What are the actual costs of tearing our dependencies? Which dependencies are worth suffering through? Perham uses the example of Net.HTTP. What do the various HTTP clients add to it? Are they just more terse, do they help to avoid various pitfalls, or do they actually &quot;abstract&quot; in such a way that they lead you to write bad code?