4 ms·
Actually they're right. It's very easy to fuck up in LINQ and end up with code that balloons memory or scales poorly for example.
by csmuk 13y ago
Actually they're right. It's very easy to fuck up in LINQ and end up with code that balloons memory or scales poorly for example.
- thomasz 13y agoNot if you know linq.
- csmuk 13y agoThat's a fairly arrogant statement. You might know LINQ but does the consumer of your IEnumerable<T>? Not all team members are equal.
- MichaelGG 13y agoI think the common sentiment is that we'd all hope to hell that we never have to work on a project so crappy that team members can't understand programming language basics.
- thomasz 13y agoMost of the problems arise from people not understanding that linq queries return iterators, not collections and therefore writing O(n²) loops. But that's not too hard to learn. Alas, if you are talking about Linq2Sql or Entity Framework, then of course you have to deal with all the typical ORM problems; but this has nothing to do with Linq.