Mood:
d'ohNow Playing: Fomented Jungle - High anxiety animals in a ruthless game of get-your-goat (the goat loses)
Topic: The Squirts
Some things you should be familiar with if you want to be able to chart MSFT's course from here out. You should take the time to read the articles pointed to by the hyperlinks in each of these articles.
February 8th, 2008
Microsoft Kool-Aid and the cloud
Posted by Phil Wainewright @ 4:46 am
March 17th, 2008
Ozzie signals Microsoft’s surrender to the cloud
Posted by Phil Wainewright @ 3:57 am
June 25th, 2008
Is Bill Gates a secret cloud convert?
Posted by Phil Wainewright @ 2:40 am
Well, hell, this can't be good.
UHHH OHHHH Who made a doody?
ADO .NET Entity Framework Vote of No Confidence
The signatories of this letter are unanimous in expressing concern for the welfare of software projects undertaken in the Microsoft customer community that will make use of the forthcoming ADO .NET Entity Framework.
We collectively urge Microsoft customers to seriously consider the concerns of a group of experts that Microsoft has called, “the technical community’s best and brightest,” and who share a deep commitment to community and a willingness to help others. We have been building entity-based applications since the initial release of .NET using both Microsoft and non-Microsoft tools, and have accumulated a tremendous amount of experience in general best practices for entity-based applications as well as best practices for entity-based applications with .NET.
Because of the technical misgivings with the Entity Framework’s current design and implementation, and the potential future risk they pose to Microsoft customer projects we respectfully submit a Vote of No Confidence for the ADO .NET Entity Framework in its current state and for the on-going challenges with the expert community feedback processes.
We urge Microsoft customers who will be considering entity architectures for their software application projects to be aware of the following unresolved issues with the impending first release of the ADO .NET Entity Framework:
Well, of course, I'll post them one at a time and see what we can see in the technological entrails, but, as a wise farmer once told me, you don't eat a prize winning hog like that all at once.
http://efvote.wufoo.com/forms/ado-net-entity-framework-vote-of-no-confidence/
"INORDINATE FOCUS THE DATA ASPECT OF ENTITIES LEADS TO DEGRADED ENTITY ARCHITECTURES:
While entities are data objects from the perspective of data storage and data storage technologies, entities are more significantly behavioral objects from the perspective of entity-oriented applications."
Read the VCSY claims construction and you will remember the explanation VCSY gives of the arbitrary object - an object which acts to keep itself informed as to maintain an always ready interface as an arbitrarily used object.
The MVP's here are complaining they do (or "did") that kind of work with Microsoft. What's up with that capability being yanked out of ADO.Net? What's up with that?
"The Entity Framework’s focus is on the support the data storage aspects of entity objects at the expense of the primary use case for entities in software applications, which is to govern business rules and business logic. Without recognizing this key architectural enabler and distinction, the ADO .NET Entity Framework team has built only half of the story into the framework..."
Uhhh ohhhh. I don't know this was designed this way by these people or this is one colosal booboo but these guys are clearly outing Microsoft's claim construction, showing Microsoft engineers know about this kind of architecture and they want to advance in it.
This reminds me of portuno's law of multiple modal opportunities: something doesn't just happen; something is caused by the something that happened before. So this one event deserves some in depth delving. I don't want to treat this one too tritely. I think we have the crack in the Microsoft dam that was bound to happen to any old, creaky and never tested bulwark.
Meanwhile, a closer look at the issues by Tim Mallalieu:
Tim Mallalieu's Blog.
Just a PM's random musings on data, models, services...
Vote of No Confidence
So,
It's been a long, long time since I have posted anything on my blog. Reality is I tried to maintain a blog where I thought I could come up with wonderfully profound things to share with the world but clearly that was not the case.
(worth the read at the URL for the technical side of the issues stated in the petition)
Sigh. You can almost hear the disappointment in the guy's heart. To have thought you were working with the world's greatest software company thinking you were going to be on the team to bring a new generation of real software advances... only to find you were a sandbag in the business of trying to get what didn't belong. That's a shame.
These are the reasons the MVP's signed the Vote of No Confidence in Microsoft's ADO.Net Entity Framework. Each of these is a description of the bottleneck encountered when you try to build an arbitrating object framework. This is the problem with traditional procedural methods in software. VCSY's patent does not block this road of development, thus is not too broad. VCSY's patent demonstrates a way to get around these bottlenecks... leaving traditional procedural software methods to do whatever they can.
Providing an advanced capability is not "unenforceable" because the advances provided by 744 stick out like a sore thumb when you don't use them.
From http://efvote.wufoo.com/forms/ado-net-entity-framework-vote-of-no-confidence/
INORDINATE FOCUS THE DATA ASPECT OF ENTITIES LEADS TO DEGRADED ENTITY ARCHITECTURES:
EXCESS CODE NEEDED TO DEAL WITH LACK OF LAZY LOADING:
SHARED, CANONICAL MODEL CONTRADICTS SOFTWARE BEST PRACTICES:
LACK OF PERSISTENCE IGNORANCE CAUSES BUSINESS LOGIC TO BE HARDER TO READ, WRITE, AND MODIFY, CAUSING DEVELOPMENT AND MAINTENANCE COSTS TO INCREASE AT AN EXAGGERATED RATE:
EXCESSIVE MERGE CONFLICTS WITH SOURCE CONTROL IN TEAM ENVIRONMENTS:
I'll fill out each of these over the next few days and show you where this element is addressed in the patent. The bottom line is Microsoft's developers just handed VCSY's lawyers a validating list identifying what Microsoft should admit and a huge opportunity only days from a point where the judge could issue a summary decision about Microsoft's claims.
Perhaps before I start fleshing out the above MVP's complaint, you should have an opportunity to see what I thought of the patent a month after it was granted in 2004. HERE
Now we can begin talking about the next world.
Woops - and let's not forget the TIMELINE
cool
hug me
accident prone
chillin'
celebratory
don't ask