3 ms·
When LINQ first came out, I personally remember creating some long rants at the bar with my drinking buddies that we didn't need no stinking FP in our OOP. I n
by JakeStone 6y ago
When LINQ first came out, I personally remember creating some long rants at the bar with my drinking buddies that we didn't need no stinking FP in our OOP.
I now find myself writing half my data processing in LINQ and find myself thankful that I can chain together a few methods on a collection with possible transformation in a line or two rather than having to write 2 or 3 nested loops with all sorts of conditionals.
I'm taking the new things that come up in C# as they come, and even the ones I don't care for, I generally end up using to some extent.
Go with the flow, or pick another language, would be my suggestion.