You might be interested in checking out the rust implementation: https://github.com/rs-ipfs/rust-ipfs
Im not actually sure how well it would work for what youre after, but it is an option!
There is a version of libp2p, which is the library used by IPFS, that is written in C++. Perhaps that is another option.
I use a text-only browser. It does not automatically source resources external to the page. I do not experience "heavy" pages. What you refer to is probably what happens when pages try to source a gazillion different resources.
24MB is just the total for the compressed packages. The ipfs binary is actually over twice that size.
(Your guess may be incorrect)
In some cases I have 24MB but I want to conserve space for other programs. The go-ipfs uncompressed binary is 56MB not 24MB.
That is a multiple times larger than the combined size of the kernel and userland I use.
Seems like making ipfs run on smaller systems is a goal some are interested in pursuing. I could be wrong but I doubt I am the the only one interested in this.
I simply cannot agree with any comments that imply that keeping size small is a worthless goal. I could list hundreds of past and current examples where people are trying to reduce size and/or complaining about large size. k/shakti fits in a 2000's-era CPU cache. Arguably it does more than go-ipfs. At least, one can certainly do more with it.
It makes no sense to argue against making programs small, for a variety of reasons I am not even bothering to mention. Large programs offer no additonal benefits. Generally, no one is forcing anyone else to use smaller, faster programs if they do not want to, UNIX utilities being one obvious exception; there are others.
I will continue to write, use and appreciate smaller, faster, more resource-efficient programs. I am not the only one. You will have many more folks than just me to convince that they should ignore size.