Hacker News Reader

Comment by Cshelton | Hacker News Reader

I mean, to be fair to them somewhat, it is in their documentation and getting started guide. They highly recommend, in a production environment, to put a .Net Core web app behind a proxy because the Kestrel server engine is so new, every case is not handled yet. I'd hope, being Microsoft, that nobody just ignored that.

View on HN

Maybe if Kestrel isn't ready yet they shouldn't be releasing it? Actually a lot of .NET Core feels half-finished.

It is an open source project, if they don't release it they cannot start receiving community feedback, patch sets, and bugs. Which means a lot of stuff still won't be found until it is released, no matter when that is.

.Net Core is definitely half baked but it is a pretty ambitious undertaking. They're completely re-developing .Net from the ground up to be cross platform, no small task.

For its intended purpose, it is ready enough and stable. But that is the point of open source as well, to have outside input into decisions made early on. Besides, is anything release actually fully ready yet? I don't think releasing it was a bad idea. .Net Core does seem to be moving fast but things are now stabilizing and it has been a combined effort of internal and external Microsoft developers, which is great for them. If they had simply released another .Net framework 5, I think a lot of developer mind share would have gone elsewhere. Open source was the right decision, and despite it feeling half-finished, it's actually a great improvement. Things will stabilize.

As of 2.0, ASP.NET Core does finally feel ready for primetime to me. I've been revisiting the whole picture periodically for 2 years, and finally the tooling seems to be complete and performant, and the end result and developer experience finally seem to have been worth all the headaches.

I don't think you've used .NET Core recently if you're saying that it feels half-finished. This is just FUD. At this point, .NET Core, especially 2.0, is excellent for almost every use case except native app development. Even then, you've got .NET Native attempting to solve that problem. The last time .NET Core was "half-finished" was probably its 1.0 release.

Have they finished Entity Framework yet?

Actually the fun topic of DB translated JOIN support was just announced as finished. Just that I do not remember for 2.0 or upcoming 2.1 release :)

Group by translation to SQL is still in the 2.1 preview. Even then it only supports grouping on columns from a single table at a time.

EF is not everyone's cup of tea. Dapper works just fine in Net Core 2.

I am still waiting for EF 6 feature parity, including DB visual designers, and Xamarin.Forms support for all .NET Core platforms.

They recommend not using Kestrel for an internet facing app and I agree. There is no reason not to use it for services that are not internet facing.

Reply on news.ycombinator.com