3 ms·
.NET's '10 tonne' standard library is a decent part of what makes it so usable. And it's not exactly massive either - I can publish a standalone .NET Core app t
by GordonS 8y ago
.NET's '10 tonne' standard library is a decent part of what makes it so usable. And it's not exactly massive either - I can publish a standalone .NET Core app that's only around 30MB in size. For the usability and GC, I'll take that over C any day.
- naasking 8y ago> I can publish a standalone .NET Core app that's only around 30MB in size. Honestly, it shouldn't need to be that big. There's plenty of cruft even in .NET core.
- rndgermandude 8y agoThat will probably come done quiet a bit when illink gets out of alpha. It is basically a tree-shaker to eliminate dead/unused stuff from the resulting standalone binary. https://github.com/dotnet/announcements/issues/30 https://github.com/dotnet/announcements/issues/30
- naasking 8y agoA tree shaking linker will definitely help a lot, but there's still some runtime baggage that probably can't be removed. For instance, dynamic loading and all of the related type and assembly metadata structures. I look forward to seeing what they can do!