Nathan J Pledger

Program.X musings from the Isle of Man concerning ASP.NET, in particular accessibility, web standards and neat ideas.

An alternative view on LINQ


I've mentioned my concerns about LINQ before, and I think this article sums them up perfectly.

http://builder.com.com/5100-6388_14-5897968.html?tag=nl.e601

My argument is just that we have built in 'good' coding practises, separating things my layers and tiers of logical and physical form, only to come full-circle and now seem to be encouraged to put psuedo-SQL in-line with our code.

Posted: Oct 20 2005, 01:05 PM by Nathan Pledger | with 3 comment(s)
Filed under:

Comments

Erwyn van der Meer said:

I am sorry to disagree. I think it's wonderful to have set-based query logic as a first-class citizen in C#. This will increase developer productivity a lot. LINQ has no dependencies on SQL. Although one form of the LINQ syntax is SQL like, it absolutely doesn't matter where the data comes from. In the case of DLINQ the queries are translated to T-SQL and executed in a SQL Server database. This will give you the same performance as calling a stored procedure.
# October 20, 2005 6:34 AM

Nathan Pledger said:

I don't dispute that it isn't really useful. It would be awesome to sort collections, etc. And I am keen to play - unfortunately I have to wait as MS didn't see fit to send me my pack - but I would be resistant to replacing my data-layer.
# October 20, 2005 11:03 AM

Olaf Conijn said:

The person who wrote this article is sooo waay off, next thing he'll tell us is that we should be able to deploy assemblies to a database ;-).

Set based operators belong in programming languages, i've actually missed them a lot in C#. Maybe looking at LINQ as 'syntactic sugar'
over C# 2.0 to make developers more productive makes this more acceptable? It really is nothing more (or less).

Unless people start to deploy shared data (databases) with client applications or load gigabytes of data into a client's memory to do datawarehouding, i think everything that whatever should be at the back stayed at the back.

You can download the LINQ compiler preview at http://msdn.microsoft.com/netframework/future/linq/
# October 20, 2005 8:43 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)