A fully self-contained natively compiled C# Hello World, including GC and everything can be as small as ~440 kB
A fully self-contained natively compiled C# Hello World, including GC and everything can be as small as ~440 kB
A fully self-contained natively compiled C# Hello World, including GC and everything can be as small as ~440 kB
To demonstrate the OS's capability and relatively small size, in the late 1990s QNX released a demo image that included the POSIX-compliant QNX 4 OS, a full graphical user interface, graphical text editor, TCP/IP networking, web browser and web server that all fit on a bootable 1.44 MB floppy disk for the 386 PC. https://en.m.wikipedia.org/wiki/QNX
Is this programming humor?
Is someone else silently crying when remembering the demo scene...?
Every demoparty in the link you mentioned with a beginning date and a dash but no end date is still happening. The demoscene is still very much alive.
This is pretty awesome and it shows how far .NET has come in recent years.
Is this supposed to be small or am I missing something? 400kb for hello world does not really sound small
What do they mean by "fully self-contained natively compiled C#"? Some executable that depends on specific update Windows versions and 30 different .net frameworks installed on the system? :D
I might be missing a joke? but they are referring to NativeAOT, aptly named as it compiles a .NET application into a native binary ahead of time (instead of using a JIT.) The benefit being no dependency on the .NET runtime, faster startup time (but slower runtime performance, due to lack of JIT), lower memory footprint, and any other advantage you'd find in Go.
The question is, how good is NativeAOT comparable to a static binary from C++ or Go? As we both know Microsoft has a very poor track record when it comes to static builds / "self-contained" stuff. My question was mostly satire but I still would like to know how "self-containted" are those applications.
Does it effectively output a single binary? Does it create some kind of clusterf*k and awkward packaging formats like other MS solutions such as UWP? Will it actually be deployable to a random fresh install of Debian 12 or Windows 10? What about compatibility with older systems?