Definitely chunky sizes, but keep in mind I'm coming back to dotnet after almost a decade. I could be measuring the wrong thing here and there could be ways to significantly shrink these sizes. Maybe.
HelloWorld console app:
Windows: 136MB
OSX: 140.5MB
Linux: 152.9MB
I don't care much about the binary size, just ease of deployment and developer UX. I enjoy writing C# so these tools are great for me.
130 MB for a hello world is a lot though, but I don't think it's the main reason why there are not many cross platform desktop apps that I know of. I suppose the reasons are others and different.
C# is light-year times different than C/C++ or any other lightweight resultant lang compilers... you know that.
Very performant when doing a mid-to-high computation apps with great async support (most langs implementations are poor in doing that).
Let alone the safety related to references 😉
So yeah, the big self-contained binaries is worth it (in many scenarios).
C# is light-year times different than C/C++ or any other lightweight resultant lang compilers... you know that.
I'm not sure I know this, I stopped using .NET a long time ago. C# is a beautiful language IIRC, it's just not my cup of tea anymore. I would probably consider re-learning it if I were writing desktop apps with a UI but I don't so it doesn't fit in my toolbox for now.
I wasn't comparing C# with anything by the way, just asked how big the binaries are :D
Very performant when doing a mid-to-high computation apps with great async support (most langs implementations are poor in doing that)
What do you mean? I know it's performant (the CLR always has been), but why do you think its async support is better than others? I'm very curious because I know nothing about it.
The binaries don't even have to be self-contained - you can install .NET Core as a package on Linux and just provide a Linux build of your application.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How big are the self contained binaries :D ?
Definitely chunky sizes, but keep in mind I'm coming back to dotnet after almost a decade. I could be measuring the wrong thing here and there could be ways to significantly shrink these sizes. Maybe.
HelloWorld console app:
I don't care much about the binary size, just ease of deployment and developer UX. I enjoy writing C# so these tools are great for me.
130 MB for a hello world is a lot though, but I don't think it's the main reason why there are not many cross platform desktop apps that I know of. I suppose the reasons are others and different.
Anyhow, if you're having fun... why not :)
C# is light-year times different than C/C++ or any other lightweight resultant lang compilers... you know that.
Very performant when doing a mid-to-high computation apps with great async support (most langs implementations are poor in doing that).
Let alone the safety related to references 😉
So yeah, the big self-contained binaries is worth it (in many scenarios).
I'm not sure I know this, I stopped using .NET a long time ago. C# is a beautiful language IIRC, it's just not my cup of tea anymore. I would probably consider re-learning it if I were writing desktop apps with a UI but I don't so it doesn't fit in my toolbox for now.
I wasn't comparing C# with anything by the way, just asked how big the binaries are :D
What do you mean? I know it's performant (the CLR always has been), but why do you think its async support is better than others? I'm very curious because I know nothing about it.
Thanks!
Finished writing an article about that before a sec:
dev.to/0xrumple/how-c-asynchronous...
The binaries don't even have to be self-contained - you can install .NET Core as a package on Linux and just provide a Linux build of your application.