The real question is, how do they know what we post? Chew on that a while .... well, they do have that unique id thing built into it ...

11.1 You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services. By submitting, posting or displaying the content you give Google a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through, the Services. This license is for the sole purpose of enabling Google to display, distribute and promote the Services and may be revoked for certain Services as defined in the Additional Terms of those Services.

Hmmm, guess we should really start to read those "I agree" thingies ....

Andrew, I was referring to our forums ;) on which I recommended LLBLGen yesterday to a guy who had to have LINQ on Oracle. We want to make money, but as a developer myself I find the need to help people trumps sales. This is why our support is so timely, when someone needs help they need it now. Thanks cowGar on the Mono compliment, on ES2009 system including the code generator we hope to make run under Mono as well. We think Mono is going places.

This is Mike from EntitySpaces, we do not boot off for folks for talking about the competition, just an FYI ....

Lambda can make code extremely hard to read as well, to me, the solution should look like the problem

Does our industry really even have breaking news?

See http://www.entityspaces.net/blog/2007/07/10/The+Google+Content+Network+Who+Is+Clicking+On+Your+Ads.aspx

How about we ask Microsoft to stop screwing around and make the product available to us? Give me a break.

It's all the disadvantages of CompuServe now available on the web ;) he he

Well, this post was not really about ES, I was just showing how to turn a LINQ query into DataTable, it's pure .NET code and there is no EntitySpaces code at all in the post. I thought it was pretty cool that you could do this and just wanted to share it. And the picture was meant to be funny.

Again, I'm shocked at your comment, it just proves you do not know what you're talking about, that is not EntitySpaces code, that's pure ADO.NET and LINQ, I was just sharing with the community how to turn a LINQ query into a DataTable, I'm sorry, but you're comment is just rotten eggs. Let's see these three posts?

? What, you must have EntitySpaces mixed up with something else? I think you missed the whole point of this post, there is no EntitySpaces code in this post and EntitySpaces is hardly being screwed up, I added support for LINQ to it in 20 minutes, it was nothing, could you please post the articles, that's pretty lame I think making such a statement.

oops, that was meant to be "his own" not "his one"

Give Frans some credit, he makes a lot of good points in there. As far as maintainability I think we ORM makers have already solved that issue including LLBLGen, I know Frans has created his one LINQ provider and also can generate the LLBLGen architecture. As for our architecture, EntitySpaces, we have added LINQ to SQL support to load our Entities and we generate from the database schema in seconds (modeling comes later). Therefore, you can do full LINQ queries with EntitySpaces and we have NO XML files to mess with or maintain such as the EF does, and we use zero reflection, run on mono, the compact framework, medium trust and so on. To us the ADO EF is just another competitor, sure many will use it, however the market is big and there is room for many. We are not sitting around wondering what the EF is doing, we are moving foward just as we always have. We absorbed LINQ and we are moving on, nuff said.

http://www.entityspaces.net/blog/2008/05/11/EntitySpaces+2008+LINQ+To+SQL+In+Next+Beta.aspx

http://www.entityspaces.net/blog/2008/05/11/EntitySpaces+2008+LINQ+To+SQL+In+Next+Beta+Part+2.aspx

The interesting thing will be to see if Microsoft "accidentally" removes the feature that allows us to leverage LINQ in this way, which is a real possibility. They pulled the ability to return a DataTable from a LINQ query in one of the beta's (hmmm?). The question is now will they track down how we are doing it and eliminate it as well.

Ya, maybe I'm paranoid but I see Microsoft co-opting the ALT.NET movement before it even hits the ground, I know one thing, I'll be off the approved speaker list faster than you can blink an eye. I hope I'm wrong but probably not. ;) I feel a blog post coming on tonight, a real rage against the macine ;(

LOL, sorry, no I was just commenting on the "the Geek Code generator put together by Scott Hanselman." I have a lot of hopes for ALT.NET and just hate to see Microsoft employees creating lists of ALT.NET technologies that list mostly other Microsoft technologies (as is true in our category). I think I have a different opinion than some folks, I view the ALT part as "Alternative" and see that evaporation somewhat but for the movement even gets moving .... Just ignore me, I work too many hours ....