Live data from Hacker News

What Makes .NET Core So Special?

blog.jamesmichaelhickey.com

191–200 of 247 posts

Re: What Makes .NET Core So Special?

#191
post #149

Earlier quoted context omitted.

Honestly, people still using the getter and setter argument in 2018 as a reason to pick a language should not be taken seriously. Indeed Java has more boilerplate, but honestly I've never been bothered by it (as you can generate most within your IDE) and because its explicitly written down it can make code more readable. And Java also has lambda's.

Yeah... the bigger reason to move away from Java isn't Getters and Setters... The bigger reason is one word: Oracle Whether you go towards C# or other companies... Oracle is a horrible company.

Oracle is only one player in the Java ecosystem. OpenJDK owns just about everything now, and most organizations are going to get support somewhere besides Oracle. There's been some good recent innovation with Java, and I think it'll continue due to the new accelerated release schedule.

That reminds me, I want to experiment some with AOT compilation and also the new GC plugins.

Re: What Makes .NET Core So Special?

#192

I want to like .Net Core, I really do. But in my opinion its just not yet ready for serious use. An example. If you want to use .Net Core you can't use entity framework, you have to use EF Core, which doesn't yet support mapping to views or stored procs, only tables. Now you might think that's fine, maybe you only want to map to tables. But it's the same story all over the ecosystem. Many major projects have a separa…

We utilize EF Core on a fairly large project and have had zero issues mapping to views. I doubt there are issues at this point with SPs either though I haven't personally done that.

EF Core has a lot of work that needs to be done (and features brought over) but for a lot of use cases, it works just dandy. I don't disagree with your comments about incompatibilities and restrictions - just wanted to set the record straight.

Re: What Makes .NET Core So Special?

#193

I want to like .Net Core, I really do. But in my opinion its just not yet ready for serious use. An example. If you want to use .Net Core you can't use entity framework, you have to use EF Core, which doesn't yet support mapping to views or stored procs, only tables. Now you might think that's fine, maybe you only want to map to tables. But it's the same story all over the ecosystem. Many major projects have a separa…

EF will be available in netcore 3.

Re: What Makes .NET Core So Special?

#194
post #54

Earlier quoted context omitted.

I'm not sure I agree that AWS and GCP are clearly better than Azure - but I'm not been neck deep in all three so I cannot definitively say so. But Azure is moving fast. > Visual Studio is littered with SQL server and Azure tools which doesn't even make sense. Either offer equal tools for all major tech or none, but this subconscious constant selling of their own tools sickens me slowly. Of course they support their o…

Live unit testing is great, assuming your company pay for the Enterprise edition which is the only one which has it. (Mine doesn't).

Check out NCrunch. It's an inexpensive add-on which does this specifically.

Re: What Makes .NET Core So Special?

#195

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…

As someone eager to start (properly) learning C#, is doing so on Mac actually viable? It sounds like it from your post but would be eager to hear your thoughts (I only have a Mac at home to practice on).

.NET Core on Mac with Rider has been great here.

Re: What Makes .NET Core So Special?

#196

Earlier quoted context omitted.

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 t…

Except EF is basically the only provider that works 100% robustly. I have some pretty bad memories of getting NHibernate's Linq provider to work correctly, since it would just randomly mistranslate queries or flat-out throw exceptions.

As someone who has switched almost entirely away from .net to go, this is absolutely untrue. I'm fairly certain the issue was PEBKAC

Re: What Makes .NET Core So Special?

#197

.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…

> I really hope the platform can break out of the Microsoft silo and attract talent from other dev communities The problem is often trust. Like so many Microsoft projects, to me the goal of .Net Core seems to be to get as much people as possible on to a proprietary language and/or get as many devs as possible onto developing stuff that doesn't hurt Microsoft. There's no guarantee that MS will not pull the plug at som…

> to get as much people as possible on to a proprietary language

The C# compiler (Roslyn) is completely free and open source, as are a number of .NET components: CoreFX - Core foundational libraries, CoreCLR - runtime.

As well as PowerShell, VS Code, Typescript, ASP.NET Core, MVC, Blazor, F#, Z3 Theorem Prover, etc.

And that's from just the first few pages of their Open Source page: https://opensource.microsoft.com/

Re: What Makes .NET Core So Special?

#198

The post only mentions .NET Core, but should actually be mostly talking about ASP.NET Core that runs on top of .NET Core. The features such as dependency injection and Razor Pages are ASP.NET Core specific. Microsoft have announced that they will be porting WinForms and WPF over to .NET Core so that they no longer need the heavyweight .NET Framework. However, this DOES NOT make WinForms/WPF cross-platform. They will…

> Microsoft have announced that they will be porting WinForms and WPF over to .NET Core so that they no longer need the heavyweight .NET Framework. However, this DOES NOT make WinForms/WPF cross-platform. They will still be restricted to Windows but will allow you the benefits of .NET Core, such as allowing side-by-side versioning. They've come back full circle to forking Java for Windows only usage. .NET is the clos…

What in the world ever happened to Xamarin? Weren't they acquired by Microsoft two years ago? I felt sure we'd have a nice cross-platform desktop GUI by now. . .

I'm feeling more fearful that they acquired Xamarin just to destroy it.

Re: What Makes .NET Core So Special?

#199

Earlier quoted context omitted.

> 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 com…

For what value of "best?" In the majority of cases, "best" is what gets the product shipping fastest. Not memory usage, not performance, not coolness. Just getting in the hands of the guys in the warehouse who are wasting time using spreadsheets, etc. The "easy, laziest option" is what gets you from 0 to full speed first.

That's what Microsoft's core customer base cares about.

Re: What Makes .NET Core So Special?

#200
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#

This needs to be brought up more. It's a huge bonus. F# is fantastic.
Post reply on HN