←back to thread

.NET 10

(devblogs.microsoft.com)
489 points runesoerensen | 4 comments | 11 Nov 25 15:44 UTC | HN request time: 0.547s | source
Show context
jcmontx ◴[12 Nov 25 12:09 UTC] No.45899182[source]▶
I've worked with .NET for over 10 years and we built our startup on top of it. Here are my thoughts:

Pros:

* Stability

* Very decent standard library

* Good balance between productivity and robustness

* Great package management

* Extremely easy to upgrade, so essentially free goodies (performance) every year or so

Cons:

* Very MSFT dominated (obviously)

* Subpar tooling outside of Windows (I'm looking at you C# Dev Kit)

* C# has way to many features, it feels bloated

* Culturally, it feels like .NET devs are less "passionate" about their work

* The freaking stigma of being a .NET dev: you will never be as cool as the guys who work with Node/Python/whatever

Edit: Also I'd like to add EFCore as one of the pros of the ecosystem. Hands down the best ORM. Others don't come close.

replies(8): >>45899274 #>>45899472 #>>45899662 #>>45899834 #>>45899898 #>>45900262 #>>45904735 #>>45908095 #
1. denismenace ◴[12 Nov 25 19:14 UTC] No.45904735[source]▶
Why is EF regarded as such a good ORM? I've encountered countless bugs in different repos related to its stateful nature after many years in .NET. Personally I found it completely illogical for my ORM to maintain state. I just want it to hold my schema and build queries.
replies(3): >>45905195 #>>45905770 #>>45906166 #
2. achandlerwhite ◴[12 Nov 25 19:38 UTC] No.45905195[source]▶
EF or EFCore? Specifically EFCore is highly regarded whereas legacy EF not so much.
3. htgb ◴[12 Nov 25 20:10 UTC] No.45905770[source]▶
Are you referring to the change tracker? FYI you can have it skip tracking as the default (or per query), but when you actually want to make changes you better opt in with `.AsTracking()`.

Anyway, I've used EF at work for about a decade and I'm happy with it. I surely have blind spots since I haven't used other ORMs in that time, but some things I like are:

- Convenient definition of schema.

- Nice handling of migrations.

- LINQ integration

- Decent and improving support for interceptors, type converters and other things to tailor it to our use cases.

What ORM do you prefer, and how does it differ by being stateless? How does saving look like, for example?

4. wvenable ◴[12 Nov 25 20:32 UTC] No.45906166[source]▶
EF Core is amazing -- in it's default setup it works for 99% of situation. For the 1%, you can basically turn off everything you don't want.