3 ms·
This Cω/LINQ concept of unifying XML and object data access with SQL- and XPath-like syntax is elegant and obvious (aka intuitive). Does it get much usage? Mo
by 6ren 16y ago
This Cω/LINQ concept of unifying XML and object data access with SQL- and XPath-like syntax is elegant and obvious (aka intuitive).
Does it get much usage?
Most XML access is delegated to tools these days, and SQL is so familiar (and type-based access so unfamiliar), that it seems unlikely to make inroads on either - nor offer substantial practical benefits. That is: no order-of-magnitude benefit to overcome barriers to adoption.
Have you personally found LINQ beneficial? Has it been widely adopted? Why/why not, do you think?
- MatthewPhillips 16y agoEveryone loves LINQ, but no one uses it because changes require redeployment and that can be costly.
- contextfree 16y ago"LINQ to Objects" (i.e. the set of standard query operators, basically map/filter/fold and sundries) is hugely beneficial and ubiquitous in the recent codebases I've worked on. LINQ to SQL and similar IQueryable providers can be useful and are used, but unfortunately still suffer from the fact that querying is just one part of an ORM solution, and the state of ORMs in general and Microsoft's in particular is still kind of a mess. I haven't seen huge resistance to adopting them though - using some kind of LINQ-based ORM is pretty standard in ASP.NET MVC projects.