You'd be surprised what ends up dragged into where when you have a build system that makes it easy. Just look at the npm.js mess (and what kind of things ended up depending on what kind of other thing) if you want an example.

Static linking will do that. Imagine you have 400mb of binary objects your app depends on. Libraries your company uses for app analytics, SSO, 2FA, Corporate service bus api, etc. You statically link all those for your 50mb Swift UI app and bam, you’re in the 700mb range.

The use of Go will definitely do that, as it prefers to statically link everything.

https://go.dev/wiki/Mobile

If we had an entire POSIX OS built with Go, then we would be back to statically-linked UNIX prior to BSD.

https://www.freecodecamp.org/news/golang-statically-and-dyna...

can you build a Swift UI in go?

There is a single mention of Swift on the developer page that I posted.

"Note that you can also invoke GoHelloGreetings from Swift by importing Hello."

  @import Hello
  // ...
  let msg = Hello.GoHelloGreetings("gopher")

Oh lord…

That's a lot of code, though. I can't imagine common libraries so big. The Linux kernel is less than 100mb.

That would be the source code. The default debian kernel is around 12 MB but it could be much smaller.

It doesn't bundle full random external libraries compiled with debugging symbols and "whatever other stuff".

The neat thing about code is that there's no upper limit on how inefficient one can get.

It's literally "work expands to fill the available time" (s/time/cycles and memory/)