Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What Makes .NET Core So Special?

blog.jamesmichaelhickey.com

Post reply on HN
Print view View original

121–130 of 247 posts

Re: What Makes .NET Core So Special?

#121

Post by gameswithgo »

a_imho wrote: post #108
aerophilic wrote: post #6

Earlier quoted context omitted.

I agree, they can do a better job articulating what is “awesome”. For me personally, there are 3 main reasons that I have been super excited about .Net core: 1. It is C#, in my opinion the best statically typed language. The easiest way I have described it to other folks is it is Java++. Combine it with really good intelligence, and it is like the code “flows out of you”. Part of the reason for that is the effort put…

For someone who is not well versed in MS world, what is the C# equivalent of the Java Streams API?

linq, kind of, but it has more run time overhead and is more flexible.

Re: What Makes .NET Core So Special?

#122

Post by macca321 »

jbergens wrote: post #100
elorant wrote: post #72

Earlier quoted context omitted.

Why should I try AWS and pay twice the price I pay in any traditional hosting provider? Don't drink the HN koolaid and thing that trying the latest and greatest will give you any real benefit. The good thing about .NET or Java or any of these seemingly uncool technologies is that they're tried and tested and work just fine. The real problem with developing in .NET is Windows. Everything else is stellar. Hopefully at…

You can already run VS Code on Linux. Or use emacs or vim and command line tools.

JetBrains have brought out a x-plat C# IDE also, called Rider. It's very nice.

Re: What Makes .NET Core So Special?

#123

Post by gameswithgo »

zamalek wrote: post #24
gameswithgo wrote: post #7

Earlier quoted context omitted.

I wonder if it is the garbage collected language with the highest performance ceiling now?

Java might still be faster, and that's deliberate. The goal of RyuJIT is understandable code and predictable machine code. HotSpot aims for performance at all costs. Many HotSpot features have been moving over to RyuJIT, even more are planned. I've always been envious of HotSpot. The main feature I've been envious of is its namesake: it aggressively optimizes hot spots. .Net now has this (tiered compilation), but it'…

.NET Core now has a ton of memory/data layout control with ref, ref returns, span and also has support for hardware intrinsics as well.

Even without the intrinsics C# is beating the JVM on the benchmark game already. Though I think those benchmarks may not all alllow hotspot to do its thing.

Re: What Makes .NET Core So Special?

#124

Post by nestorD »

cryptos wrote: post #80

Besides Node.js the main competitor is is Java/JVM. C# is a bit nicer than Java, but you can use Kotlin or Scala on the JVM. All in all I see no real advantage over the JVM/Java world - more of the other way around, since the .Net ecoystem is not as big as the JVM ecosystem. However competition is always good.

> C# is a bit nicer than Java, but you can use Kotlin or Scala on the JVM.

With .Net you get F#

Re: What Makes .NET Core So Special?

#125

Post by scarface74 »

Jallal wrote: post #118
scarface74 wrote: post #97

Earlier quoted context omitted.

I'm talking about the developers who never discovered ORMs until MS pushed theirs Because every ORM sucks outside of the ones built on top of Linq. Linq is great because it makes a query language a first class citizen and it decouples writing the query and the implementation.

In all fairness, you should consider Entity Framework, not Linq, when speaking about ORMs. And the first versions of EF sucked compared to the others frameworks that were available at the time.

It’s not just about EF. The beauty of C# and Linq is:

Linq => expression trees => provider => native query language of data source => data source.

Written correctly, you can pass expressions around like:

repo.Find(c => c.age > 65 && c.gender == “male”)

And the expression can be interpreted at runtime by either EF creating native sql or the Mongo driver creating a native MongoQuery or even an in memory List for unit testing.

No matter how good another ORM may be for another language, what made C#s implementation better was Linq + expression trees.

Re: What Makes .NET Core So Special?

#126

Post by batty_alex »

hvidgaard wrote: post #106
oblio wrote: post #63

Earlier quoted context omitted.

Resharper has it for a fraction of the price.

I really like ReSharper, and I've bought it for my team, but it often makes VS crawl like the PC was a budget model from 2000. They must address this sooner or later.

I just cut out the middleman and use their Rider IDE. It doesn't seem to bring my whole PC to grinding halt and is built on top of ReSharper. It's worth a try if you haven't checked it out already.

Re: What Makes .NET Core So Special?

#127

Post by nicoburns »

MarvelousWololo wrote: post #110
smashedtoatoms wrote: post #73

I’m in the process of porting a bunch of go code to dotnet core 2.1 on AWS lambda. I’m on a Mac using vscode. I never installed mono, just the dotnet sdk. Honestly, I’ve been amazed at how good the tools have been. For cli and serverless dev, it’s been surprisingly great. It’s fast. C# is decent. The cold starts are not as fast as go, but not terrible. Memory usage is low. It’s been a legitimately positive experience…

I'm complete new to C# and Java but I'm looking into them to choose a new language to learn. I'm mostly worried about memory consumption since I often use a cheap $5 VPS. Would you happen to know which one would be a better fit for my use case? Thank you.

If you're worried about memory usage, then neither is great (C# is a little better than Java), you may want to look into Go or Rust.

Re: What Makes .NET Core So Special?

#128

Post by gjm11 »

On an entirely superficial point, in case the author is reading:

> It offers developers modern tooling that can scaffold projects, build, run, test and deploy using incredibly easy-to-use CLI tools.

I think this is one place where the abbreviation CLI should be avoided, since it means two completely different things both of which are somewhat plausible here at first glance. "Command line interface" -- even though this is a Microsoft-derived thing, you can do everything using the command-line tools you're used to from Unix, node.js, etc.; "Common Language Infrastructure" -- even though this is happening on Mac and Linux as well as Windows, you can do everything using the Microsoft .NET tools you're used to from Windows. I'm pretty sure the first of these is the intended meaning, but I had to think about it.

Re: What Makes .NET Core So Special?

#129

Post by meddlepal »

MarvelousWololo wrote: post #110
smashedtoatoms wrote: post #73

I’m in the process of porting a bunch of go code to dotnet core 2.1 on AWS lambda. I’m on a Mac using vscode. I never installed mono, just the dotnet sdk. Honestly, I’ve been amazed at how good the tools have been. For cli and serverless dev, it’s been surprisingly great. It’s fast. C# is decent. The cold starts are not as fast as go, but not terrible. Memory usage is low. It’s been a legitimately positive experience…

I'm complete new to C# and Java but I'm looking into them to choose a new language to learn. I'm mostly worried about memory consumption since I often use a cheap $5 VPS. Would you happen to know which one would be a better fit for my use case? Thank you.

If you want to be on the JVM I highly recommend giving Kotlin a look before Java. Great language and excellent tooling.

Re: What Makes .NET Core So Special?

#130

Post by endorphone »

thepp1983 wrote: post #46
dustinmoris wrote: post #42

.NET Core and F# are the only reasons why I still develop .NET. I really hope the platform can break out of the Microsoft silo and attract talent from other dev communities, because the biggest problem with .NET Core, despite the whole OSS move, is still that the majority of C# developers let themselves happily trap by the Microsoft marketing machinery. The average .NET developer never even tries different things lik…

> The average .NET developer never even tries different things like AWS or the Google Cloud, TravisCI or AppVeyor, etc. They just swallow anything which so-called MVPs and conference presenters force them down the throat, primarily Azure which is by all measures inferior to the other two and they don't even know. I've made an account because this attitude irritates me. 1. This is patently untrue. The real reason is t…

I do agree that the person you replied to was unnecessarily cynical (and quite irrational -- there is nothing surprising that Microsoft pitches Microsoft services in their own products), but your reply is contradictory.

I've worked in a variety of shops, both "Microsoft" shops and non-Microsoft shops, and I would most certainly agree with the GP That Microsoft shops tend to be dominated by developers who like the comfort of just eating whatever pablum Microsoft is serving, often even if that pablum will take years longer to digest than competitive alternatives. There is, in general, a tunnel vision that profoundly limits the options available to build solutions, at substantial project cost.

And it's understandable. If you're at a Microsoft shop you aren't going to challenge the norm if your first choice is SQL Server and BizTalk and Azure, etc. It's the easy, laziest option. Occasionally it might be the best option, but that's just accidental given that the choice was predetermined.

Post reply on HN