There is a point in moving the FROM ahead of SELECT and getting sensible auto-complete suggestions from your IDE as you type.
LINQ, however, attempts to solve a much bigger problem:
Use consistent code to process data and don't worry whether it is in a remote database or in a local array.
If you manage to do it in a way that
- integrates seamlessly with e.g. Python IDE and I don't have to pass and parse strings
- allows me to access graph, document and relational data
- allows me to pull and process the data from REST APIs, [O/J]DBC and straight from my RAM
- and maybe even includes deductive (PROLOG/DATALOG) features
LINQ, however, attempts to solve a much bigger problem: Use consistent code to process data and don't worry whether it is in a remote database or in a local array.
If you manage to do it in a way that
- integrates seamlessly with e.g. Python IDE and I don't have to pass and parse strings
- allows me to access graph, document and relational data
- allows me to pull and process the data from REST APIs, [O/J]DBC and straight from my RAM
- and maybe even includes deductive (PROLOG/DATALOG) features
I will be your most loyal client