3 ms·
Of 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
by Daishiman 16y ago
Of 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.