Actually........
It's more generic than that. It's C#'s monadic comprehension syntax ala Scala's for and Haskell's Do.
It works on more than just IEnumerable, it actually works on anything that implements Select, SelectMany, and Where...
I wish they would at least alias map, reduce, some, etc.
It makes sense to use terms that many C# (and SQL) users are already familiar with, rather than terms that they may not know of.
I think this is mostly because I'm still not comfortable with the syntax, and partly because of the set/iterative impedance mismatch that is there. "It's not you, LINQ. It's me."
Agreed. I've transitioned to spending most of my time in JS, and wherever I can I use .map(), but the chaining it's not quite the same as LINQ. Someday I intend to write a library of Array addons to provide GroupBy and so on, but I can't imagine it'll be super efficient.
_([ ... ]).map( ... ).filter( ... ).value()
It's not exactly extending the native array...but there are far fewer side effects to doing it this way.
I almost feel a bit gross when I have to write a "foreach" loop at this point, because there's almost always an equivalent way to do it in LINQ (although it's a tradeoff, as the one downside of LINQ is that given it's deferred nature, it's harder to debug).