1. 11
  1.  

  2. 4

    This seems neat.

    If I understand the release notes and the design document, running the self-contained executable for the first time will extract the contents of the archive (200+ files) to the disk. Not a terrible thing, but it’s something to keep in mind.

    1. 1

      Very interesting. I do not see any additional files in the folder of the executable on either the Windows or Linux systems, but I’m sure they go into an appdev type temp folder. So maybe not a truly self contained exe, but pretty close.

    2. 2

      I really don’t get this fear of installing dependencies (provided they’re managed by the system and not strewn across language-specific ones, eahc with their own conventions and likely pollution of system namespaces…) or something other than one giant blob of an executable - is typing in yum/apt/dnf/apk/whatever install libfoo before running that bad? Or even just shipping an archive with the libraries included?

      1. 2

        I’ve been fretting over the fact that the dead simple server I wrote in Common Lisp (SBCL) compiles to a 70MB image (10MB after gzexe). But seeing that Hello World in .NET Core compiles to a 30MB executable makes me feel a lot better about it. I don’t feel like I’m Doing It Wrong.

        Note: my first computer that was my own had a 100MB hard drive. So I still feel like I’m Doing It Wrong.

        1. 1

          dotnet publish -r win-x64 -c Release /p:PublishSingleFile=true

          Is there a technical reason for the curveball argument format?

          1. 2

            Looks the same as MSBuild arguments so probably just that reason.