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

171–180 of 247 posts

Re: What Makes .NET Core So Special?

#171

Post by javcasas »

alexmuro wrote: post #140

Personally the biggest advantage .NET core has for my situation is that it creates a pool of programming talent and mindshare that I'd now be open to hiring and working with on projects that can now be made with open source tools in a sane environment. I don't think it would be my go to choice for projects currently, but its an option I would happily consider and I give Microsoft a lot of credit for moving in this di…

For us, hiring .NET core developers is very hard. The pool of programming talent is gigantic, but it's also full of ultra-low quality developers. It has taken us almost half a year to find a decent C# .NET developer, with an average of 2 interviews per week on the best developers we could find. Meanwhile the previous developer had time to construct a behemonth of Java overengineering (Enterprise code they call it) that is taking us several months to tear down. We couldn't fire him because we didn't have a replacement, but in hindsight, firing him soon would have been better.

@alexmuro: best of luck finding quality in the pool of programming talent.

Re: What Makes .NET Core So Special?

#172

Post by MiyamotoAkira »

scarface74 wrote: post #96
BurnGpuBurn wrote: post #87

Earlier quoted context omitted.

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

Microsoft just announced that .Net Framework is in maintenance mode. The future is .Net Core. Over half of the VMs running on Azure are Linux. Microsoft knows that the future is not selling Windows licenses.

Sorry, could you please link to the announcement?

Agree about the Windows licenses.

Re: What Makes .NET Core So Special?

#173

Post by ajryan »

bungie4 wrote: post #164

I just inherited a .Net core app that was a proof of concept. It's a real pot luck of glued together functionality. I remember working in MS ASP land almost 2 decades ago and I swore I wouldn't invest a single minute learning another proprietary MS technology. I by and large held to that but here I sit, banging away at some C# code. This is day 3. Did you know if you specify a path in JSON and apply it to Use app.Use…

You could replace .NET core in this comment with any $framework and see plenty examples of developers misusing a tool.

Re: What Makes .NET Core So Special?

#174

Post by ajryan »

sebastienros wrote: post #162
morrbo wrote: post #158

Earlier quoted context omitted.

I'm a huge C# advocate but we actually went the other way. Regardless of the tooling etc. we still have to use Golang for mission critical stuff. This is mainly due to the cold start times you mentioned - mainly the "first request" problem C# has with web related requests. I've been keeping up with the latest developments, and it seems that they're finally starting to address the problem with tiered compilation stuff…

You can usually cut the cold start performance in half by enabling Tiered Compilation. It's just one parameter in your project file, or via an environment variable. Disclaimer: I work on performance in the ASP.NET team.

What are you disclaiming?

Re: What Makes .NET Core So Special?

#175

Post by smashedtoatoms »

morrbo wrote: post #158
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 a huge C# advocate but we actually went the other way. Regardless of the tooling etc. we still have to use Golang for mission critical stuff. This is mainly due to the cold start times you mentioned - mainly the "first request" problem C# has with web related requests. I've been keeping up with the latest developments, and it seems that they're finally starting to address the problem with tiered compilation stuff…

Yea, this project is mostly batch processing of things, so cold starts don’t matter. There is one api endpoint that we left in go for quick responses. I thought about doing a C# to js transpile, but have not had time to look into it. That being said, our cold starts are < 2 seconds with dotnet core 2.1, which isn’t great, but isn’t too bad.

Re: What Makes .NET Core So Special?

#176

Post by gameswithgo »

SimonPStevens wrote: post #160

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…

Maybe you will find that rolling a little of your own code instead of depending on libraries as much is less hard than you imagined and has some nice benefits?

EF isn't a necessity, many shops prefer not to use it at all.

Core is the future so if one wants to keep using .NET at all they should find a way or switch to something else.

Re: What Makes .NET Core So Special?

#177

Post by rpeden »

EdgarVerona wrote: post #31
soulwatcher wrote: post #4

Many of the features (Dependency injection, etc) seem only to be available for ASP.Net Core. What about cross platform desktop applications? Do we have a GUI layer that is cross platform as well?

Oh, the dependency injection definitely works independently of ASP.NET Core - it's just something frequently talked about in tandem with it. Just wrote a console app that used it a couple of days ago. I don't know about the current status of the GUI layer, other than that I've heard plans for WPF to be ported over to .NET Core. I don't know if or when that will actually happen.

Both WPF and WinForms will be part of .NET Core 3.0. They've done a few demos of it already, and were able to port over existing apps without any changes to the code. This even worked when using third party controls like the ones you can get from Telerik. They just added references to the Telerik .dll's they already had, and everything just worked.

They'll still only run on Windows, but it's a nice option for teams that want to move their existing apps over to .NET Core and take advantage of the quicker update cycle and improved performance.

Re: What Makes .NET Core So Special?

#178

Post by TylerH »

bungie4 wrote: post #164

I just inherited a .Net core app that was a proof of concept. It's a real pot luck of glued together functionality. I remember working in MS ASP land almost 2 decades ago and I swore I wouldn't invest a single minute learning another proprietary MS technology. I by and large held to that but here I sit, banging away at some C# code. This is day 3. Did you know if you specify a path in JSON and apply it to Use app.Use…

by and large, btw

Re: What Makes .NET Core So Special?

#179

Post by davedx »

SimonPStevens wrote: post #160

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…

I'm working on a fairly complex e-commerce platform built on .Net Core, I'm really happy with it. We use EF core too.

It's a pretty serious project, and for us, the benefits of our developers being able to natively develop on Macbooks and being able to deploy to Linux containers outweighs missing features.

Swings and roundabouts...

Re: What Makes .NET Core So Special?

#180

Post by oaiey »

dev_north_east wrote: post #133
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…

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

Totally. .NET Core SDK, VS Code and the C# VS Code plugin are enough.
Post reply on HN