bloat always does have some reason. but it's still bloat. Good engineering makes good tradeoffs, rather than throwing in everything anyone wants. (Not that I

bloat always does have some reason. but it's still bloat. Good engineering makes good tradeoffs, rather than throwing in everything anyone wants. (Not that I think this effort in go is "awesome". For one, it's probably bigger executables than even statically linked coreutils. The suckless sbase/ubase have some real potential though.)