Well as someone with 25 years SQL experience, I generally will still use LINQ for 90% of db access code in business style applications, for very important reaso

Well as someone with 25 years SQL experience, I generally will still use LINQ for 90% of db access code in business style applications, for very important reasons beyond those mentioned, like - They may realise value in having a compiler provide guarantees, as a bonus immediately in a tight feedback look while editing code as well as on compilation - They have favour expressive languages with robust error handling, integrated IDE and VC etc - They may want to reduce the number of moving parts These are all along the themes of a) delivering results faster, and b) improving the maintenance lifecycle of systems - unlike those parts of the industry that don't really plan to maintain their systems and instead just wanna do rewrites in the latest hotness which is usually a hot mess from a long term maintainability perspective.