All I can read in the entire thread is about added
1) Management problems
2) Administration problems
3) More complexity
Above three signifies the major headache if Exchange is integrated with SQL Back-End box.
Tell me honestly, how many of us who were spoon fed with GUI based features got a major set back when we found powershell owning 80% of the operations on E12 (and further on E14). Didn't we sit down and read and learn and ogt over the problem.
To backup with facts E12 is a hot selling cake for Microsoft (I do not have access, else I would have given an estimate sales figure for E12).
So, if there is improvement I think MS should think on terms of SQL. ESE/Jet has its own major disadvantages - not many of you realize that DB on Jet goes beyond corruption in many cases - Here Jet engine (along with PSS) will tell you SORRY and your DB is gone for good. Jet Engines has the problem with Named Property since ages.
Some one above did mention - why did MS come up with such a announcement when it could not provide facts backing its news. It is something of sort tomorrow MS might release noather statement E14 is better than E12 - on what terms, on what basis - if not revealed whats the use of this announcement.
(Off-the topic) recently NASA + ISRO guys announced water on Moon, didn't they mention about the satellite, the mission, the date time (and other specifications etc). Cmon, MS you guys dont need to start more speculation about an on-going affair since past 5-10 yrs.
Get rid of the Rumour once and for all with facts in front of the world.