i'm programming in Go now it feels like they've mashed the worst parts of C and Javascript syntax together, with the package dependency hell of early-2010s Ruby, and the elitist community of early-2000s Linux fanboys oh, and Google owns it
-
Show this thread
-
Replying to @AmyZenunim
Don't forget the garbage collector from Java and the static linking of... 70s UNIX? Though, having worked at Google, I can see how it works for *them* in some contexts :-)
4 replies 4 retweets 54 likes -
Replying to @marcan42 @AmyZenunim
giving me a static binary i don't need to worry about is the only thing i, an amateur who doesn't write programs, like about Go
2 replies 0 retweets 21 likes -
Replying to @atomicthumbs @AmyZenunim
Static binaries are great for toy projects or for companies like Google who recompile and redeploy everything constantly. For everyone else, they are a huge security liability as dependencies get linked in and never updated. Patching a dependency means updating *all* dependents.
3 replies 1 retweet 26 likes -
I'd generally take "linked in and never updated" over dynamically linked against libraries that aren't on the user's system or with versions of libraries that haven't been tested. Has statically linking with the *option* to dynamically link at runtime been tried yet?
1 reply 0 retweets 2 likes
No, Go always statically links all Go code as far as I know.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.