undefined | Better HN

0 pointsalmosthere1y ago0 comments

.NET executables requires a runtime environment to be installed.

Go executables do not.

TSC is installed in too many places for that burden to be placed all of a sudden. It is the same reason why Java has had a complicated acceptance history too. It's fine in the places that it is pre-installed, but no where else.

Node/React/Typescript developers do not want to install .net all of a sudden. If you react that poorly, pretend they decided they decided to write it in Java and ask if you think Node/React/Typescript developers WANT to install Java.

0 comments

afavour1y ago

FYI this hasn’t been the case with C# for a very long time now.

vips7L1y ago

.NET has been able to build a self contained single file executable for both the JIT and AOT target for a quite some time. Java also does not require the user to install a runtime. JLink and JPackage have both been around for a long time.

mytec1y ago

Yes, but they may not always work. While generally true there are still some edge cases.

SQL Server connections are one example where I do get .exe with the .pdb in the publish directory but the .exe won't run correctly without the "Microsoft.Data.SqlClient.SNI.dll" file.

Another example are any libraries that have "RequiresDynamicCodeAttribute" requirements.

yakz1y ago

Maybe some other runtimes do this or it has been changed, but in the past self-contained singe-file .NET deployment just meant that it rolled all the files up during publishing and when you run it, it extracted them to a folder. Not really like a single statically linked executable.

webprofusion1y ago

You can indeed produce a compiled native executable with minimal bloat: https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

vips7L1y ago

It hasn't done that in years.

estebarb1y ago

C# AOT filesizes are huge compared to Go.

MStrehovsky1y ago

Do you have data backing that up? Per https://github.com/MichalStrehovsky/sizegame:

C#: 945 kB Go: 2174 kB

Both are EXEs you just copy to the machine, no separate runtime needed, talks directly to the OS.

1 more reply

j / k navigate · click thread line to collapse

0 pointsalmosthere1y ago0 comments

.NET executables requires a runtime environment to be installed.

Go executables do not.

0 comments

afavour1y ago

FYI this hasn’t been the case with C# for a very long time now.

vips7L1y ago

mytec1y ago

Yes, but they may not always work. While generally true there are still some edge cases.

SQL Server connections are one example where I do get .exe with the .pdb in the publish directory but the .exe won't run correctly without the "Microsoft.Data.SqlClient.SNI.dll" file.

Another example are any libraries that have "RequiresDynamicCodeAttribute" requirements.

yakz1y ago

webprofusion1y ago

You can indeed produce a compiled native executable with minimal bloat: https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

vips7L1y ago

It hasn't done that in years.

estebarb1y ago

C# AOT filesizes are huge compared to Go.

MStrehovsky1y ago

Do you have data backing that up? Per https://github.com/MichalStrehovsky/sizegame:

C#: 945 kB Go: 2174 kB

Both are EXEs you just copy to the machine, no separate runtime needed, talks directly to the OS.

1 more reply

j / k navigate · click thread line to collapse