News for hackers. Stuff that matters.

A comment on Diving into Go by building a CLI application. Parent comment

Re:Diving into Go by building a CLI application by Cthulhu_ on Wednesday May 27, 2020 @03:50AM (#23320512)
Node is nice, but maybe a bit verbose and the CLI utilities are a bit low-level. The main downside to Node is that you need an external runtime to run your applications.

But I guess the counter-downside to Go is that you need to compile different versions for different platforms; the binaries are not portable.

[ Parent | on HN ]
Re:Diving into Go by building a CLI application by pansa2 on Wednesday May 27, 2020 @03:55AM (#23320543)
> Go [...] binaries are not portable.

Maybe not, but Go has excellent support for cross-compilation. You can still support users on multiple platforms while only developing and building on one.

[ Parent | on HN ]
Re:Diving into Go by building a CLI application by eryb on Wednesday May 27, 2020 @05:24AM (#23321079)
Binaries are obviously not portable, you can't run ARM binary on x86 and vice versa without emulation.

Unlike any other language Go lets you create binaries for almost all architectures and OS with a single command, you won't find this in any language.

[ Parent | on HN ]
Re:Diving into Go by building a CLI application by sagichmal on Wednesday May 27, 2020 @07:10PM (#23331301)
> But I guess the counter-downside to Go is that you need to compile different versions for different platforms; the binaries are not portable.

Why is this a downside? Native binaries are the Platonic ideal for distributing applications.

[ Parent | on HN ]