Somewhat 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…
Reducing Tailscale’s binary size on macOS
21–30 of 34 posts
Re: Reducing Tailscale’s binary size on macOS
#221.5 MB for a stub binary which does nothing but load and call a symbol from another file seems a little excessive in its own right.
Re: Reducing Tailscale’s binary size on macOS
#231.5 MB for a stub binary which does nothing but load and call a symbol from another file seems a little excessive in its own right.
The main binary also contains Tailscale’s GUI (onboarding, auth, menu, notifications, etc) so it does a little more than that.
Re: Reducing Tailscale’s binary size on macOS
#241.5 MB for a stub binary which does nothing but load and call a symbol from another file seems a little excessive in its own right.
The main binary also contains Tailscale’s GUI (onboarding, auth, menu, notifications, etc) so it does a little more than that.
Re: Reducing Tailscale’s binary size on macOS
#25Earlier 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.
Re: Reducing Tailscale’s binary size on macOS
#261.5 MB for a stub binary which does nothing but load and call a symbol from another file seems a little excessive in its own right.
Re: Reducing Tailscale’s binary size on macOS
#271.5 MB for a stub binary which does nothing but load and call a symbol from another file seems a little excessive in its own right.
Agreed. Strangely discussions of bloat sometimes trigger snarky replies: https://news.ycombinator.com/item?id=34732782
hard to take seriously the idea that 11MB is bloated in a normal linux server or user desktop environment
Re: Reducing Tailscale’s binary size on macOS
#28Somewhat 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…
Re: Reducing Tailscale’s binary size on macOS
#29Earlier quoted context omitted.
Calling dlopen is perhaps one of the slowest way to bring in libraries on Darwin.
What would you recommend? dlopen is only used when running in CLI mode (which is not super performance sensitive), but not making it slower than it needs to be would be good too.
Re: Reducing Tailscale’s binary size on macOS
#30Earlier quoted context omitted.
Agreed. Strangely discussions of bloat sometimes trigger snarky replies: https://news.ycombinator.com/item?id=34732782
bloated is relative and subjective but the only context where an 11MB binary could be considered bloated is embedded hard to take seriously the idea that 11MB is bloated in a normal linux server or user desktop environment