4 ms·
I think this along with the other answers discussing the difficulty remembering the specific arguments of `reduce` (especially when varying by language!) are ke
by wingman-jr 17d ago
I think this along with the other answers discussing the difficulty remembering the specific arguments of `reduce` (especially when varying by language!) are key reasons. After reading this conversational thread, I think maybe Microsoft got it right with LINQ:
- `Where` is perhaps more intuitive than `filter`
- `Select` seems no worse than `map` by invoking SQL-like syntax
- While `reduce` is preserved as `Aggregate`, provide `GroupBy` and other handy methods as the preferred methods. In the code I write, it's probably these other methods that get called 95+% of the time. Who wants to `Aggregate` when they can simply `Sum` for example?
- int_19h 15d agoLINQ was very intentionally designed to use SQL terminology for this because at the time (to remind, this was 2007), your typical C# or VB developer had no clue whatsoever about functional programming and the usual terminology there, while SQL knowledge would be much more widespread.