How external ORMs simplify anything when you have to cope with complex XML configuration like the Java EJBs ? Complexity just hide somewhere else. Moreover It introduces dependencies on External 3rd parties above the dependencie to Microsoft. So where's the advantage ?
+1
A:
With which ORMs are you dealing with complex XML? That is hardly "normal" for ORMs and it's generally not the only option.
A good ORM simplifies your life significantly, it doesn't make it more complicated.
You don't have to take a dependence on any library you are willing to code yourself. They are called reusable components for a reason.
Go ahead and start from scratch or use one of the inadequate ORMs from Microsoft (since it seems as though you've accepted that dependency), it sounds like you have plenty of time to reinvent the wheel.
Michael Maddox
2009-09-20 09:35:13
If it was so simple then why Martin Fowler says it's too complicated :)http://www.infoq.com/presentations/domain-specific-languages
programmernovice
2009-09-20 15:15:53
I'm not watching a 25 minute video. If you have a specific part to point out, let me know. DSLs are different from ORMs, so I'm not sure why DSLs would be relevant here.
Michael Maddox
2009-09-20 16:29:09
A:
An ORM is trying to solve the mistmatch between the way a database works,stores and returns information and the way we want our code to work, store data and manipulate that same data.
This is not a solved problem and the tools are changing and improving. Every decision in this area usually involves a trade off and in order to balance the design tradeoffs you do have to understand more of the history of what problems each ORM is trying to solve before writing it off as too complex.
At the end of the day, an ORM is there so you can use code instead of writing it from scratch.
For more on this type of discussion, check this Coding Horror post.
Nat
2010-07-19 21:58:23