I dunno, to me being bloat free isn't the same as having few features - it's more about how tight those features are, how thinly they are implemented, and how much it avoids creeping into additional things once it has reached high feature density in the initial narrow focus. E.g. I wouldn't consider curl bloated. It supports damn near every transfer protocol a lunch table of engineers could think to name, has a boatload of options and knobs to do what you want with all of those, and is hundreds of thousands of lines of code... but at the same time is ultimately a couple of MB, sticks to the narrow job of "transferring data with URLs", and keeps a simple interface without feeling the need expand to be the place to go for every related task too like e.g. a bloated browser would.