.NET

1503 readers

3 users here now

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements

Related communities

Wikipedia pages

.NET (open source & cross platform)
.NET Framework (proprietary & Windows-only)

founded 2 years ago

MODERATORS

erlingur

starman

Spyros

What do you find most frustrating about .NET? (programming.dev)

submitted 2 years ago* (last edited 2 years ago) by sisyphean to c/dotnet

35 comments fedilink hide all child comments

The original thread is on the devil’s website and I don’t want to direct traffic to it, so here’s a link to the tweet instead:

https://twitter.com/davidfowl/status/1671351948640129024?s=46&t=OEG0fcSTxko2ppiL47BW1Q

you are viewing a single comment's thread
view the rest of the comments

[–] douglasg14b 2 points 2 years ago

Performance limits of LINQ...?

You're getting nearly the same performance out of loopes generated by LINQ as you would normal for loops.

If you're referring to LINQ and EF Core, you're generation SQL with it, not running LINQ. And that query generation is incredibly performant these days (I think EF 7 was something like 5% slower than dapper?).

So luckily you can squeeze a ton of performance out of it!