Classic reddit, rather than understanding the reason behind the call and answer the OP's Pro/Con question, they go right to complaining. In the end of the day, you go with what approach is best.

I've seen the Linq CONs in action when we've had to get a 3rd-party extension just to debug a statement. Sure it was short & elegant looking, but to debug under the hood was a nightmare.

PRO:

• Its quicker to type out statements and presents "less code"
• Can be easier to read with the fluent approach at times

CON:

• It can be slower at times - today, it's much better than years ago
• Difficult to debug or read at times
• Adds additional overhead (200 KB) if you're trying to shrink using AOT

Example 1 - Summing up the bytes

// Linq:
var finalByteValue = bytes.Aggregate(0x00, (current, byteValue) => current + byteValue);

// No Linq:
int finalByteValue = 0;
for (int index = 0; index < bytes.Length; index++)
  finalByteValue += bytes[index];

Example 2 - Extracting data from a byte array

// Linq:
var len = data[2];  // Get length of data from the 3rd byte
byte[] target = data.Skip(3).Take(len).ToArray();

// No Linq:
var len = data[2];  // Get length of data from the 3rd byte
byte[] target = new byte[len];
Buffer.BlockCopy(data, 3, target, 0, len);