I'll paraphrase - some in the Oracle community feel that Linq is largely a fad... one of the things they've been critical of (which I share at this point) is the sql code that linq to sql generates.OK. I'm glad you say "at this point" - whenever I express an opinion I try to say "in April 2007" or "today" rather than slating a new technology in its immature form. But I'm very surprised to hear that the Oracle people would be forming fixed opinions before they can see what it generates against Oracle. Are you sure about that?
But for those who have been writing stored procs, I really don't believe they'll be in a mad rush to start using linq to sqlClearly, if they've already decided it's a fad, or inefficient, or whatever. ;-) But as I said earlier, you *can* use SPs via Linq to SQL. The two aren't mutually exclusive.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
