4 ms·
> no more having to deal with dependencies at runtime So, it is the same that linking the libraries statically? C and C++ has done that like since forever.
by pmelendez 11y ago
> no more having to deal with dependencies at runtime
So, it is the same that linking the libraries statically? C and C++ has done that like since forever.
- StavrosK 11y agoHey, if you said "written in C", I would be similarly excited about its ease of deployment.
- rakoo 11y agoVery true, I had python and ruby in mind. What Go makes different still is that static linking is mandatory.
- FooBarWidget 11y agoHave you ever actually tried producing a statically linked C/C++ binary? I've been programming in C/C++ for 10+ years. Static linking is a huge pain. My latest efforts have led me to create holy build boxes inside carefully controlled Docker-based environments just to be able to produce binaries that work on every Linux. With Go you can just run a single command to cross-compile binaries that work everywhere. Minimal setup required, no expert knowledge required.
- pmelendez 11y ago> Have you ever actually tried producing a statically linked C/C++ binary? Many times actually, I prefer to deploy just one file whenever I can. > just to be able to produce binaries that work on every Linux That's a Linux design/decision thing. Linux binary compatibility is ... well ... challenging. In Windows is not hard at all (Not sure how is it in MacOS since I have worked mostly for iOS in Apple's world).
- nl 11y agoThat sound like pretty strong agreement, unless you are just targeting Windows?