Earlier quoted context omitted.
It could also be a legacy of a lot of the team coming from Google, which statically links everything except glibc.
I'm surprised Google isn't using musl then at this point.
Musl is slow.
Reducing Tailscale’s binary size on macOS
31–34 of 34 posts
Re: Reducing Tailscale’s binary size on macOS
#32Guys, please figure out a way to reduce your footprint on openwrt. 11452 -rwxr-xr-x 1 root root 11.2M Sep 1 2021 /usr/sbin/tailscaled 7612 -rwxr-xr-x 1 root root 7.4M Sep 1 2021 /usr/sbin/tailscale I love tailscale, but it forces me to use usb sticks on most of my openwrt routers.
There is a way to build an even smaller version of Tailscale for embedded systems, though there are some trade offs with regards to ease of use and security. https://tailscale.com/kb/1207/small-tailscale/ has more details.
Method described gets most of the win from UPX.
That's not applicable on openwrt as it already uses lzma on filesystem level. Switching to UPX would cause excessive ram usage as binary would be in anonymous memory and no longer be backed by filesystem pages.
Re: Reducing Tailscale’s binary size on macOS
#33I'm surprised they didn't go for the binary size analysis tools like
https://github.com/google/bloaty
Or goweight.
Re: Reducing Tailscale’s binary size on macOS
#34Somewhat tangential, but ever since a recent update of the MacOS tailscale client, I've been unable to connect to any other exit nodes. I click on the exit node I'd like to connect to and it just silently fails. I tried making a shortcut as well that would connect to that node and it also fails. I've verified the exit node itself is working correctly on other devices, it only fails on the Macbook. Has anyone else enc…
One change that went into 1.36 is that you can no longer use an exit node while advertising one (https://github.com/tailscale/tailscale/issues/3569). The Mac UI was not updated for that in time, but the next release the menu items should be disabled correctly.