[Analemma_]

Same for Visual Studio (the full one, not VSCode). I think this just the nature of these giant IDEs that let you target multiple OS versions: if you want to faithfully target/simulate multiple operating systems, you need both the OS binaries and the platform libraries for each of them. As the saying goes, couple gigs here, a couple gigs there, and soon you're talking about real disk space.

[alkonaut]

VS can be pretty small, but there are 1000's of optionals. My 2019 Enterprise with lots of boxes checked is 6Gb (in the program dir, it also has some runtimes etc outside.).

Considering the last patch for just one of the games I play was 50+ Gb, it's pretty reasonable...

[vbezhenar]

If you'll carefully maintain your Android Studio installation, it's not that bad. People usually installing multiple SDKs, images which take quite a lot of space.

[kllrnohj]

The system images are the big ones. The SDK + sources for a given platform isn't that big, like ~100MB. The system image + saved emulator state is easily ~2-5GB though.

[ploxiln]

Check out Zig: in less than 50 MB, it supports cross-compiling on any major os/arch for any other major os/arch, and it compiles most plain C code, and it includes libc headers for linux/mac/windows.

https://ziglang.org/download/ https://ziglang.org/#Cross-compiling-is-a-first-class-use-ca...

50 million bytes is really a lot of bytes, it's just that everyone has become accustomed to orders-of-magnitude bloat, and doesn't realize the 100x duplication and inefficiency which sneaks into just about every part of computing where it can get away with it.

[bathtub365]

This appears to just be a programming language with very limited frameworks compared to those provided by Android and iOS. For example, where are the GUI toolkits, audio toolkits, robust storage frameworks, 3D capabilities, etc? This doesn't seem like an accurate comparison at all. Sure, you can get down to 50MB if you throw out all the features.

[kbumsik]

Zig is just a language compiler, isn't it? It is comparable to clang, gcc, or Visual C++ compiler. Why are you comparing it with a fully featured IDE?

[ploxiln]

... because it was claimed that the IDEs are many gigabytes because they "let you target multiple OS versions". Well, you can get the required essence for targeting multiple operating systems and architectures in 50 MB. If a "proper IDE" for a single OS/arch/platform is 500 MB, then one for "multiple" could be about 550 MB. So how does it get up to 5 GB or more? Convenience and junk.

[genocidicbunny]

Just because Zig can compile for multiple platforms, doesn't mean it can target those platforms like those IDEs could.

For example, with Visual Studio, a large part of the installation footprint are the various SDKs you need to actually build a realistic Windows application (that interacts with the OS, maybe does some COM stuff, brings up a GUI, uses networking..etc) There are also multiple versions of these SDKs, especially the Windows SDKs. Visual Studio also supports a lot of languages, and for some of these languages, there is support going back to very old versions and tech stacks. You can still build Windows XP compatible applications in modern Visual Studio versions.

Can Zig talk to COM? Can it set up a DXGI swap chain? Can I pop up notification toasts as simple as calling one function? How do you package Zig apps for the Microsoft Store?

So yes, you can compile Zig programs for multiple platforms, and these can run on those platforms. But once you start getting into actually interacting with those platforms, you will need all those things you call convenience and junk. Libc is just a fraction of what you need to make applications for a platform.

[elorant]

Visual Studio has a big footprint only if you choose to install everything. I don't see the point in doing so. Are you developing for every available platform and in more than one language?