G
Guest
Hi All,
I want to start some kind of debate or poll on Linq, the question is:
Do you think is a good idea to work with Linq in the future?
Most of the articles out there are not very impartial, and are embracing
Linq as an evolution, while MVPs or wannabes are making tutorials as they go,
without questioning themselves (at least not publically): Is the best way to
go?
As the intro in the article:
http://msdn2.microsoft.com/library/bb308959.aspx, "After two decades, the
industry has reached a stable point in the evolution of object-oriented (OO)
programming technologies", instead of recollecting the benefits at this point
of OO and n-tier architectures, there is an growing interest of taking an
step back.
What is the reason to query on objects, for example, the query should be
done at a lower layer, right?
This is an open debate, but keep it clean!
Regards to all and happy programming
I want to start some kind of debate or poll on Linq, the question is:
Do you think is a good idea to work with Linq in the future?
Most of the articles out there are not very impartial, and are embracing
Linq as an evolution, while MVPs or wannabes are making tutorials as they go,
without questioning themselves (at least not publically): Is the best way to
go?
As the intro in the article:
http://msdn2.microsoft.com/library/bb308959.aspx, "After two decades, the
industry has reached a stable point in the evolution of object-oriented (OO)
programming technologies", instead of recollecting the benefits at this point
of OO and n-tier architectures, there is an growing interest of taking an
step back.
What is the reason to query on objects, for example, the query should be
done at a lower layer, right?
This is an open debate, but keep it clean!
Regards to all and happy programming