3 ms·
Haha, LINQ is the best part of the framework. It was in part designed by Erik Meijer and Don Syme(who are big names in functional languages community). LINQ to
by borisk 16y ago
Haha, LINQ is the best part of the framework. It was in part designed by Erik Meijer and Don Syme(who are big names in functional languages community). LINQ to objects and to XML are widely used. There are hundreds of non-Microsoft LINQ providers, like LINQ to Amazon.
Generally LINQ is about higher order functions, monad pattern, map-reduce. Have you tried it? It's fantastic.
- Daishiman 16y agoOf course I have. It's great, but it's only marginally better than other ORMs for my use cases (I know it's technically much more than an ORM). The time I gain writing LINQ queries is lost trying to deploy that solution, or attempting to debug marginally complex queries, something that's generally easier on dynamic languages. SQLAlchemy is still my favorite ORM around. On the same vein, while C# is an excellent language, there's too many sections of .NET and Silverlight that depend on type casting to the point where there's no advantage to using a statically typed language. And unfortunately neither IronPython nor IronRuby are used in the mainstream.
- Encosia 16y agoI think what borisk is pointing out is that LINQ isn't an ORM. It's a language feature. You're thinking of LINQ to SQL, specifically.