Why did Microsoft make the Entity Framework open source?
-
I'm actually truly curious, not trying to incite anything here. Given that this seems to be a cornerstone of data access technology for a lot of companies, I can see both benefits and drawbacks to having a community-modifiable code base, much like one would experience with any open source effort. But there's something that leaves me feeling a bit queazy, that, well, my data and the data transactions are potentially fubar'd by community changes. Not to say that Microsoft isn't (as demonstrated historically) capable of fubar'ing anything that I rely on when they come out with the next version, but still, what I wonder about is, does the Entity Framework team carefully review changes and incorporate them into the official release ? By the way, has anyone actually looked at the code? I briefly looked at it last night, and yikes, it would take a lot of effort to get familiar enough with the code for me to even feel comfortable making minor changes. There is a huge unit test code base, which probably is good, but I haven't looked at whether it's actually useful, but I would hope so! http://entityframework.codeplex.com/[^] Marc
Reverse Engineering Legacy Applications
How To Think Like a Functional Programmer
My Blog
Computational Types in C# and F#For things that Microsoft are providing that they see as "adding extra value" and "not aligned with our core revenue streams", they have made a decision to provide these technologies as open source. This means that things like EF and ASP MVC are now open source projects. This is a very good way for them to overcome the hostile reception they have had in the OS community in the past, while ensuring that they can entice a new generation of people to be locked into the MS stack.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
I'm actually truly curious, not trying to incite anything here. Given that this seems to be a cornerstone of data access technology for a lot of companies, I can see both benefits and drawbacks to having a community-modifiable code base, much like one would experience with any open source effort. But there's something that leaves me feeling a bit queazy, that, well, my data and the data transactions are potentially fubar'd by community changes. Not to say that Microsoft isn't (as demonstrated historically) capable of fubar'ing anything that I rely on when they come out with the next version, but still, what I wonder about is, does the Entity Framework team carefully review changes and incorporate them into the official release ? By the way, has anyone actually looked at the code? I briefly looked at it last night, and yikes, it would take a lot of effort to get familiar enough with the code for me to even feel comfortable making minor changes. There is a huge unit test code base, which probably is good, but I haven't looked at whether it's actually useful, but I would hope so! http://entityframework.codeplex.com/[^] Marc
Reverse Engineering Legacy Applications
How To Think Like a Functional Programmer
My Blog
Computational Types in C# and F#Marc Clifton wrote:
would take a lot of effort to get familiar enough with the code for me
The same applies to any Open Source framework. Source is mainly to figure out specific issues. Very rarely I have modified any thing is an open source code. I rather worked around the issues in my own code after looking at the portions of the open source code which caused issues.
-
Oh thank god they took it open source, I have a senior dev agitating to use EF and a policy that says we cannot use open source code. The rel problem is that I think he may have an excellent case for us to go EF, now to make the decision weather the storm of getting the policy changed/exceptioned is worth it!
Never underestimate the power of human stupidity RAH
Could I suggest an alteration to the policy: No open source unless the quality is managed by a reputable vendor. And you can maintain a list of reputable vendors...
____________________________________________________________ Be brave little warrior, be VERY brave
-
Oh thank god they took it open source, I have a senior dev agitating to use EF and a policy that says we cannot use open source code. The rel problem is that I think he may have an excellent case for us to go EF, now to make the decision weather the storm of getting the policy changed/exceptioned is worth it!
Never underestimate the power of human stupidity RAH
Why do you have such a policy? Having a policy of does it work / is it supported / is it secure makes sense. It's like having a policy to only eat in restaurants where the chefs don't have books out, or else to cook only ready meals / self-invented concoctions.
-
Marc Clifton wrote:
does the Entity Framework team carefully review changes and incorporate them into the official release ?
That would worry me. I really like EF. One of the reasons I like it is because I should be able to use and forget. It's plumbing and I don't really want to have to think about it once I start using it. Still, it might be beneficial if bugs are caught and fixed; perhaps they'll get turned round a bit quicker than the usual MS release cycle. I'd just like to know that they've been properly tested.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
Hi Mark (or anyone else using EF) Can I be a bit cheeky & ask you to have a look at this question in the .NET Framework forum please (I couldn't find a more relevant forum). http://www.codeproject.com/Messages/4385113/Entity-Framework-Import-Function-Stored-Procs-Data.aspx[^] I'm hoping for pointers to how I'm not understanding how it should work, or what I have missed to tie things together. Apologies for polluting the Lounge - feel free to ignore. Regards, Stewart
-
I'm actually truly curious, not trying to incite anything here. Given that this seems to be a cornerstone of data access technology for a lot of companies, I can see both benefits and drawbacks to having a community-modifiable code base, much like one would experience with any open source effort. But there's something that leaves me feeling a bit queazy, that, well, my data and the data transactions are potentially fubar'd by community changes. Not to say that Microsoft isn't (as demonstrated historically) capable of fubar'ing anything that I rely on when they come out with the next version, but still, what I wonder about is, does the Entity Framework team carefully review changes and incorporate them into the official release ? By the way, has anyone actually looked at the code? I briefly looked at it last night, and yikes, it would take a lot of effort to get familiar enough with the code for me to even feel comfortable making minor changes. There is a huge unit test code base, which probably is good, but I haven't looked at whether it's actually useful, but I would hope so! http://entityframework.codeplex.com/[^] Marc
Reverse Engineering Legacy Applications
How To Think Like a Functional Programmer
My Blog
Computational Types in C# and F#Providing us the code helps them to fix bugs and introduce new features slowly. Though, I really think its a ploy to have us write their API documentation. MS documentation in many of their 'open source' projects has been weak. Nothing worse then hitting F1, seeing the basic generated help text with no solid examples, references, or why's the item even exists.
-
I'm actually truly curious, not trying to incite anything here. Given that this seems to be a cornerstone of data access technology for a lot of companies, I can see both benefits and drawbacks to having a community-modifiable code base, much like one would experience with any open source effort. But there's something that leaves me feeling a bit queazy, that, well, my data and the data transactions are potentially fubar'd by community changes. Not to say that Microsoft isn't (as demonstrated historically) capable of fubar'ing anything that I rely on when they come out with the next version, but still, what I wonder about is, does the Entity Framework team carefully review changes and incorporate them into the official release ? By the way, has anyone actually looked at the code? I briefly looked at it last night, and yikes, it would take a lot of effort to get familiar enough with the code for me to even feel comfortable making minor changes. There is a huge unit test code base, which probably is good, but I haven't looked at whether it's actually useful, but I would hope so! http://entityframework.codeplex.com/[^] Marc
Reverse Engineering Legacy Applications
How To Think Like a Functional Programmer
My Blog
Computational Types in C# and F#You're right and it raised some eyebrowes here too. We feel EF is the best DAL that Microsoft has ever created. Just hope they don't drop it for some new intests in JavaScript and friends. We are a little worried that MS might not realize they have finally created a great set of tools for developing applications and go off in some weird direction chasing down some new language fad. XAML, EF, VS, C# should rule for business apps (and more) for a long time. I saw a suggestion that MS should put the CLI in the BROWSER! Why not? Cheers to all.
-
Oh thank god they took it open source, I have a senior dev agitating to use EF and a policy that says we cannot use open source code. The rel problem is that I think he may have an excellent case for us to go EF, now to make the decision weather the storm of getting the policy changed/exceptioned is worth it!
Never underestimate the power of human stupidity RAH
¿Why not use open source?, i believe the open source community have made great tools and libraries that help you better than most closed source projects, our own policy is that we use open source as long as it's license is compatible with closed source projects, and if it's not we consider a commercial license, if available.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Why do you have such a policy? Having a policy of does it work / is it supported / is it secure makes sense. It's like having a policy to only eat in restaurants where the chefs don't have books out, or else to cook only ready meals / self-invented concoctions.
For legal reasons. There may be unknown patented code in the open source or the company may find something in the combined code base that is patentable. With any open source code in the mix, then the legal group cannot create patents on the new code/algorithm. Damned patents.
-
For legal reasons. There may be unknown patented code in the open source or the company may find something in the combined code base that is patentable. With any open source code in the mix, then the legal group cannot create patents on the new code/algorithm. Damned patents.
If you build on someone's framework then you take on some liability. End of story and open/closed source changes nothing. As for your company's ability to patent work, that remains a non-issue with open vs closed. Now if you are talking about not working with GPL code because your company doesn't want to release, that actually could make some sense. But being open source does not equate to GPL or variants thereof.