These were my original worries, but as a human CLI user I notice no start-up time impact; I am certain if you benchmark it then there will be a small delay, but it's well under the human perception limit.
Runtime performance, ditto. As always, YMMV and do your own due diligence! On Saturday 15 June 2024 at 12:01:40 UTC+1 Tobias Klausmann wrote: > Hi! > > On Sat, 15 Jun 2024, Peter Galbavy wrote: > > If end binary size is a constraint, try "upx" to compress the end > binary. I > > regularly get 3x compression - but lose all debug options, obviously. > Works > > on most OSes for executables. > > Be aware that there are further consequences to using upx, beyond "no > debug symbols". Startup is likely slower, and even steady-state runtime > performance may suffer (this is anecdotal, but I have no reason to doubt > it). > > For embedded systems and similar scenarios, it still is a very valuable > tool. > > Best, > Tobias > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/9bac833d-aa58-468b-b7ba-b0a03b278b38n%40googlegroups.com.
