CBOR support uses `go-codec` which adds bloat to the binary

[drasko]

As noted here: ugorji/go#295

[ugorji]

See ugorji/go#295 (comment)

[ugorji]

Also see https://github.com/ugorji/go#managing-binary-size

[fluffy]

So should we add something to the instructions to tell people about how to turn off fast-path or what is your suggestion on this?

[ugorji]

It's your call. See https://github.com/ugorji/go#managing-binary-size

We have trimmed it down from 11MB to 5.7MB, by default. If that is still much, you can get it down to 2.9MB by using the notfastpath tag (but you sacrifice some performance as noted).

You can put that in your instructions or in your build script or something. Or you can just leave alone be if 50% savings is good enough for you. I think it is.

[drasko]

@fluffy I was capable to compress binary significantly with strip and then upx. I need to see if these tools are smart enough to remove unused portions of code (I am also using goweight to see what has been compiled in).

I think one solution might be making lightweight Go CBOR implementation (I have one in C, and it does not look so difficult to make, but will take some time). But I am not sure that even that in the end would be better than just having @ugorji 's implementation without fastpath.

[ugorji]

@fluffy @drasko Can you please take capture sizes with the latest code (that includes ugorji/go@a2154fa) and capture sizes before strip/upx, and then with strip/upx. I would like to see how much space these are taking now.

Thanks.