Running the executable: `./helloworld` Also note that, before building the executable, I tried running with `go run`, which of course, failed. I can't even say "Failed" because the go compiler was not throwing any error like *Hey, since I need to download some dependencies even though your program doesn't have one, you might wanna try running the program later.* The cursor just stuck in the terminal for eternity. I had to quit it with Ctrl + C.
On Thursday, April 9, 2020 at 4:15:50 PM UTC+6, Brian Candler wrote: > > On Thursday, 9 April 2020 06:15:22 UTC+1, Tanmay Das wrote: > >> I also forgot to mention one thing. I was able to build the program using >> go build. Even the executable was there. It just didn't run until I >> connected to internet. >> >> > When you say "it just didn't run", do you mean with "go run ...", or > directly running the executable that you just built? > > If running the already-built executable hung, then I can only guess that > Apple are using a central service to check the fingerprints of executables > that haven't been seen before. It would be interesting to run tcpdump at > the same time, to see if it's trying to do DNS lookups for some Apple > server. > > I also remember there are settings where you can send Apple information > about which applications you run (e.g. Preferences > Security & Privacy > > Privacy > Analytics > Share Mac Analytics). But I'd be surprised if it did > that *before* the application started. > -- 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/a8ba39d2-c874-42e1-a256-46ae77cd2e11%40googlegroups.com.
