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

111–120 of 247 posts

Re: What Makes .NET Core So Special?

#111

Post by barrkel »

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, the IEnumerable extension methods, and IQueryable extension methods.

Re: What Makes .NET Core So Special?

#112

Post by Crosseye_Jack »

smashedtoatoms wrote: post #78
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…

1st million calls on lambda are free... then ~$1.80/million calls/month after that. No ops once you deploy... like none. Dotnet runs on it fine after being written on a Mac, with code completion and linq hints etc. No visual studio in site. I didn’t even install mono. Your uncool technologies might be cooler than you think. ;)

Are you forgetting the API gateway charges? API gateway add’s $3.50 per million requests to the price.

Re: What Makes .NET Core So Special?

#113

Post by BjorksEgo »

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?

having a look at it, it seems like LINQ?

Re: What Makes .NET Core So Special?

#114

Post by arethuza »

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?

I had no idea what Java Streams was (a long time since I wrote much Java) and it appears to be the Java version of LINQ:

https://www.foreach.be/blog/java-and-net-comparing-streams-l...

Re: What Makes .NET Core So Special?

#115

Post by lazulicurio »

BurnGpuBurn wrote: post #87
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…

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

> But right now .Net Core feels like it's been developed by Microsoft, not like it's open source

This is my biggest reason for losing enthusiasm for .Net Core. Despite all the noise about open sourcing the development on GitHub, it still feels like Microsoft treats .Net like a Microsoft platform, not an open platform. And I'm not talking about Windows vs Linux. More that the design direction for .Net seems to be largely set by internal Microsoft politics. For example, the recent ASP.NET Core running on .Net Core vs .Net Standard decision seems to be driven by how tightly tied the .Net Core runtime is to its underlying OS.

Compare to Java with the JCP (because Java is often compared to C#). The JCP is far from perfect (e.g. all the drama with modules). But, regardless of my views of Oracle, when I'm using Java I don't worry as much that I'm tying the long-term stability of my tech stack to the whims of a single company (even with the new JDK licensing snafu).

On a side note, I'm really confused when I see people talk about how great the new tooling is. Sure, the dotnet CLI tool does more out of the box. But it still can get hairy very fast because of all the design baggage it inherited and shoved under the covers with the fancy new SDK abstraction. And Microsoft keeps cramming more and more complexity into NuGet which makes it a pain to integrate with third-party tooling.

Lastly, for the record, this isn't an anti-Microsoft rant. I think they've done a lot of great work with .Net Core---the standard library updates, cross-platform runtime, Roslyn---and I still am very productive writing .Net for my day job. Like I said, I've just lost my enthusiasm.

Re: What Makes .NET Core So Special?

#116

Post by wisam »

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?

I would say IEnumerable interface.

Re: What Makes .NET Core So Special?

#117

Post by hvidgaard »

arethuza wrote: post #107
oblio wrote: post #85

Earlier quoted context omitted.

Let's say they get it at an 80% discount. VS Enterprise apparently is now available only though a cloud subscription worth ~$3000 per year so it would still be ~$600. Resharper is $299/$239/$179 (1st/2nd/3rd year). And this is a scenario where your company can get an 80% discount (not sure this is doable) plus Resharper has a perpetual license you can keep after 1 year, just without updates.

It was a big multinational - that kind of money was literally a rounding error.

It might be a rounding error, but none the less, if they negotiate a reduced price, that would literally pay the cost of hiring a person whose only job is to do just that.

Re: What Makes .NET Core So Special?

#118

Post by Jallal »

scarface74 wrote: post #97
bonesss wrote: post #58

Earlier quoted context omitted.

IMO the issue isn't MS, really (though parts of the org are still worthy of strong skepticism), it's the cultural phenomenon of a certain generation of developers who essentially eat, breathe, and die by Microsofts product cycles... There are those argued that any innovation is unneccesary until MS launches a product for it, when it becomes a "must", ad nauseum. I'm talking about the developers who never discovered O…

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.

Re: What Makes .NET Core So Special?

#119

Post by Crosseye_Jack »

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…

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

It makes sense for them to offer tooling for their own services but that doesn’t mean they don't support other software / services as well as their own.

I can still use MariaDB with Entity Framework and push changes to the schema with update-database.

Visual Studio has extension support so 3rd party devs can add to it because MS might not be the best people to build the tool for a 3rd party, the 3rd party might just well be.

AWS provide an extension for managing AWS though Visual Studio called [0]AWS Toolkit which makes pushing code to lambda a breeze.

[0] https://aws.amazon.com/visualstudio/

Re: What Makes .NET Core So Special?

#120

Post by kankroc »

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 your end game is working professionally just check what is more in demand in your geographic location.

Personal opinion

C# is a lot better than Java. You have less boilerplate code (getter and setter in 2018, really?) and lambdas are great.

But really both are similar so you can pretty much just start with one and still find your way in the other.

Post reply on HN