Live data from Hacker News

.NET 8 Standalone 50% Smaller On Linux

learn.microsoft.com

141–150 of 179 posts

Re: .NET 8 Standalone 50% Smaller On Linux

#141

What the .NET team does on the technical side is almost universally wonderful. They've (ironically?) been a bit more successful than the Java folks at establishing multiple serious languages of different kinds running on and interoperating via the same runtime. But it's still a Microsoft project and their sword keeps looming over its head. There have been some heavy-handed anti-developer choices in the past and one c…

> bit more successful than the Java folks at establishing multiple serious languages of different kinds running on and interoperating via the same runtime

But there was plenty of serious alternative languages running on the JVM? Scala, Kotlin, Clojure. All of which have more adoption than F#.

Re: .NET 8 Standalone 50% Smaller On Linux

#142

Who is using .NET on Linux? I'm interested to hear success stories. Sounds like a a great way to build and deploy applications.

41% of EVM nodes on Ethereum run .NET on Linux via Nethermind(https://github.com/NethermindEth/nethermind).

Ethereum has a Market Cap of $249Bn and $34bn of other assets in smart contracts.

So you could say .NET on Linux has under management $116Bn and handles $800m of asset transfers per day, napkin math

Re: .NET 8 Standalone 50% Smaller On Linux

#143
post #139

Earlier quoted context omitted.

not OP, but I'd guess they are referring to F# and C# interoperability. It's trivial to call into each other from within the same project. I'm not as familiar with this on the JVM side myself. How easy/common is it to have multi-language projects? Because in .NET it's very common to have C# interface to F# projects and vice versa with minimal work.

It’s extremely easy. I have no idea what OP is talking about. I currently work on a mixed scala/java project. It’s also one of the biggest features of Kotlin, interoperability is seamless.

I regularly program in both Scala/Java and F#/C#. Interoperability in both is excellent. But I would not call it “trivial” in the Scala/Java case. Calling Scala code from Java is occasionally a pain (the converse is easy); however I don’t think I’ve ever had an issue calling F# code from C#. I think most of the friction wrt Scala lies in the fact that Scala reinvented the wheel in several places (eg collections; “operator overloading”) which are not obvious to use in Java.

Re: .NET 8 Standalone 50% Smaller On Linux

#144
post #7

Earlier quoted context omitted.

I wish people stopped using Medium for writing, it's a horrible reader experience.

I know right... I clicked through (after logging in) only to get "The author made this story available to Medium members only."

You can use the main link if you don't like Medium. It directs you to release notes.

Visiting my article is absolutely optional: https://tomaszs2.medium.com/net-8-standalone-net-apps-now-50...

Re: .NET 8 Standalone 50% Smaller On Linux

#146
post #10
post #2

[flagged]

I second the request to not use medium. There are tons of better options. Neocities, bear blog, mataroa blog, and so on. There is no reason to suffer with medium and all the nagging.

You don't have to visit my article, the main release note is linked in the main topic.

My article is available here: https://tomaszs2.medium.com/net-8-standalone-net-apps-now-50...

Re: .NET 8 Standalone 50% Smaller On Linux

#147
post #143
post #139

Earlier quoted context omitted.

It’s extremely easy. I have no idea what OP is talking about. I currently work on a mixed scala/java project. It’s also one of the biggest features of Kotlin, interoperability is seamless.

I regularly program in both Scala/Java and F#/C#. Interoperability in both is excellent. But I would not call it “trivial” in the Scala/Java case. Calling Scala code from Java is occasionally a pain (the converse is easy); however I don’t think I’ve ever had an issue calling F# code from C#. I think most of the friction wrt Scala lies in the fact that Scala reinvented the wheel in several places (eg collections; “ope…

Of course. But that isn’t the fault of the JVM or Oracle. That’s the language designers that made Scala. Look at Kotlins interop. It is rather seamless.

Re: .NET 8 Standalone 50% Smaller On Linux

#148

Who is using .NET on Linux? I'm interested to hear success stories. Sounds like a a great way to build and deploy applications.

We already had a huge C# console project originaly developed for windows/.net framework 4.5 ..

.net on Linux was a zero cost transition, giving us a whole new platform, a whole new user base. It was that easy.

Re: .NET 8 Standalone 50% Smaller On Linux

#149

Earlier quoted context omitted.

C# approach to concurrency has always been better since its introduction. It does have Channels which offer more focused pattern for SPSC, MPMC, etc. scenarios but neither Java nor Go offer a comparable level of ease of use as C#’s hot-started tasks: // The tasks will run in parallel var data = service.GetData(id); var user = service.GetUser(name); Handle(await data, await user); Re: the above comment on switching to…

There is no async coloring in Go. In the example you cited above, service.GetData can be a plain synchronous function in Go. You don't need to distinguish between sync/async as this is defined by the caller and not by the callee. Any function can be made asynchronous without changing its signature. That's one of the critical advantages of having first-class concurrency. There is no "function coloring". The simplicity…

Async coloring is a good thing (imo)

Re: .NET 8 Standalone 50% Smaller On Linux

#150

Earlier quoted context omitted.

Aside from syntax preferences, why and when would one choose Go over C#?

From my experience golang uses less memory than a .net app. I haven’t done a recent comparison so if someone had tested this lately and has different results I’d love to see it.

When C# is AOT compiled, the memory footprint is roughly the same.
Post reply on HN