Why does Zig make Docker irrelevant

Re:Why does Zig make Docker irrelevant by _gerald_ on Thursday October 20, 2022 @07:55AM (#33273303)

It is. The guy is pushing a narrative. It's still a good idea to Dockerize your apps even if they are statically compiled. If your app has C dependencies e.g. libxml2, it won't run on another system if the required C headers are missing.

Another good reason for using Docker with Zig is shareability since Zig doesn't have a package manager.

[ Parent | on HN ]

Re:Why does Zig make Docker irrelevant by kristoff_it on Thursday October 20, 2022 @11:47AM (#33276474)

Go is only statically linked when not depending on C code, if you're using CGo, you cannot get a statically linked executable with Go alone, and a lot of Go projects do depend on C code. You also lose Go's cross-compilation when using CGo.

In fact, Zig is used in combination with CGo to create statically linked executables and re-enable cross-compilation: https://dev.to/kristoff/zig-makes-go-cross-compilation-just-...

Same also applies to Rust: https://actually.fyi/posts/zig-makes-rust-cross-compilation-...

> It's still a good idea to Dockerize your apps even if they are statically compiled. If your app has C dependencies e.g. libxml2, it won't run on another system if the required C headers are missing.

You clearly don't understand the meaning of statically linked nor how dynamic linking works. Spend less time concern-trolling and more learning software engineering, friend ;^)

[ Parent | on HN ]