3 ms·
But don't try and drag the language down because you find it difficult. Oh give me a break. My exact complaint about LINQ is the opposite -- that it makes expe
by corresation 13y ago
But don't try and drag the language down because you find it difficult.
Oh give me a break. My exact complaint about LINQ is the opposite -- that it makes expensive operations seem simple, which with all innovations in language means that mediocre programmers will start abusing it in all codebases.
LINQ has a place. To say that one should be using it "all the time", however, is exactly as I said -- a canary in a coal mine. The only time I've ever come across the extensive use of LINQ it has been in horrific code.
- jmcqk6 13y agoSo I'm guess you haven't done any programming with the reactive extensions yet?
- corresation 13y agoAnd why would you guess that? Because I don't consider LINQ of Rx observers being a magic cure-all? In fact, LINQ on Rx is a symptom of the classic LINQ issue -- don't have subscriber or source filtering, or coherent, useful events -- simply broadcast everything and through the magic, free filtering of LINQ all is solved in the consumer.