[douche]

It makes a lot of sense in .NET land, because it maps to SQL, which people tend to have some kind of grasp on.

Although that LINQ expression syntax can go die in a fire. It's a great way to end up with people using borked up joins in Linq-to-SQL and EF that don't work the way they think they do, rather than the actual foreign-key relationships.