To me , that has almost NOTHING to do with NHibernate.
I mean sure, strongly typed. But you can't compare that LinqToSql to NHibernate .
You can compare the ToSql part with NHibernate and say : it produces better querys(or not) and compare mapping styles and what you can do with them.

There already is a project LinqToNhibernate. Then you will have type safety.

Sirrecco, I (the author) never sold the article as a comparison. A comparison would definitely be an interesting post, maybe that's next. But if so I would definitely not put "Expression Trees" as the first two words in the title of the post.

You do bring up a good point about LINQ to NHibernate allowing strong typing, that would have been worth mentioning. Of course I get frustrated with NHibernate enough alone without adding an additional layer of abstraction between it and the database. But it would have been a good addition to the article.

Incidentally feel free to post on the blog itself in the future, I really do like the dialog aspect of blogging as much as anything else.

I have in fact posted it :) , and yes, there is the Expression Trees thingy in the title , but i felt the accent was on LinqToSql vs NH . And I am really liking NH :P.
Can you tell ? ;)

Anything which says that one technology solution is "better than" another just isn't worth reading.