1. 39
  1.  

  2. 15

    I want to reiterate - please tell the Go team if you can share concrete problems, or if you found something you could do but was too hard to do. A lot of Go team members work at Google which has a ton of different processes and specialized tools for everything and might not understand how you are using or trying to use Go.

    If you don’t want to share publicly you can email me privately - kevin@burke.services

    1. 4

      Thank you for the hard work, it’s a beautiful programming language!

      1. 2

        I want to use Go also on embedded devices where I work, but the executable sizes are currently too large. For example, 10MB is too much for a small utility, but 1MB would be passable. Unless there are some tricks I have missed (I have tried stripping the ELF files, ++), a request for having a build flag for generating tiny executables is in the pile.

        1. 1

          You could dynamically link your binaries, thus reducing the binary size a lot https://stackoverflow.com/a/30488222

          1. 1

            That’s a good tip, I will try that. What I was originally thinking about was something similar to GCC’s -Os for size optimization, but for Go. Perhaps that’s already possible?

            1. 1

              As far as I remember, the go compiler already uses and enables a handful of binary size optimization by itself.

      2. 6

        Immutable values has my vote as most useful but underrated addition

        1. 3

          I’d agree, but the request is for concrete problems that might be solved by them.