|
|
We are rebuilding our primary application at work, and someone has thrown a monkey wrench in my view of the world and how software should be written. Monkey wrenches are not necessarily bad, if your machine is strong enough, it will just grind them to bits. They are good though in that they force the machine to at least pause and realize, if only for a second, that there is something else out there, and it needs to be assessed.
Todays monkey wrench is NHibernate, its an ORM tool that I'm told will make my life easier. (I'm an enterprise Library guy by the way, and have taken a glancing look at LINQ) To be honest, I'm skeptical, the demo code we were presented with didn't work, the wiki on the hibernate site has a ton of "It ain't workin'" comments all over the place, but I trudge on.
When I'm lost, I ask Google, Google knows all. So I ask Google "NHibernate worth it?" It's an old post, but the comments here seem to think so, and Ben's followup posts, which multiplied until he was writing sample code might lend some credence to it's value. This guy replaced his data layer in a couple of days without bitching. This guy speaks some truth, not just on ORM, but anything techy for that matter, but he likes the tool.
There is a really interesting discussion in the comments of this post of Oren Eini, and in fact all of his many posts have great content for NHibernate. Here's a link to a query generator written by the Oren dude I just talked about. Apparently, he's the shit. (by the way, I just had to add "shit" to my Live Writer dictionary, unreal.)
Stop the presses! Required reading found HERE! All 9 parts. (currently reading...very nice work...) ...which leads me to a good Best Practices article....
Enough, I'm BugEyed, tired, getting this hot laptop off my...well...off my lap. I'm in. Not even gonna look at DLinQ. I want this.
By hank on 9. October 2007 15:37 | Comments (3)
|