3 ms·
Same goes e.g. for Linq. I know of people who would prefer screen-filling methods of multiple nested loops with throwaway datastructures and various checks spri
by btschaegg 9y ago
Same goes e.g. for Linq. I know of people who would prefer screen-filling methods of multiple nested loops with throwaway datastructures and various checks sprinkled on top to a simple three-liner Linq expression.
Funnily enough, their argument always seems to be "it's easier to read this, since I'm accustomed to
for (x;y;z) if (foo ||(bar && baz)) lorem = ipsum;
as a pattern."
- dep_b 9y agoI can only imagine they got scared after seeing the SQL performance of Linq to SQL and all Linq to ORM based stuff after that.
- animal531 9y agoAgreed. But on the other hand I also find that writing code is the same as speaking normal language. We each have our preferences, vocabulary, diction, style etc. I also jumped on the Linq wagon, but cringe when I see for example a Swift etc. reducer. So as long as that person writes his page of code at a decent pace with limited/no bugs I won't hold it against him.