Microsoft aims to show Windows 7 'readiness'
After getting dinged for constantly changing plans with Windows Vista, Microsoft is taking the opposite approach with Windows 7.
The software maker is being extremely conservative with what it says publicly about the operating system--a move it says is deliberate.
"The lack of a predictable schedule combined with the churn of features late in the the process made it hard for partners to know is this the real Windows Vista," said Mike Nash, Microsoft's vice president for Windows product management. "The result of our lack of predictability was everybody (saying) 'Let's wait for this thing to stop spinning.'"
With Windows 7, Microsoft has tried to share details only as they became relatively certain. The hope is that even though Microsoft isn't talking as early about its plans, it is talking with more certainty when it does speak.
That move has led to far fewer changes in plans--but also means that Microsoft is still hedging on key questions--in particular, when Windows 7 will ship.
Microsoft has said only that it will ship within three years of the mainstream launch of Windows Vista--essentially by January 2010. However, the company is widely seen as trying to get Windows 7 on machines in time for this year's holiday season.
Without being any more specific on dates, Microsoft is trying to get its partners to make sure their software and hardware is ready for the new operating system. Although Windows 7 doesn't introduce the kinds of major changes that Vista represented versus Windows XP, the company does need hardware and software makers to double check that their Vista-compatible stuff also works with Windows 7.
On Monday, Microsoft is announcing the Windows 7 Readiness program, an effort to formalize that process. In an interview, Nash said the company hopes that by speaking about the product only as details have been nailed down, the company will restore credibility with its partners.
Those who take part in the readiness program will have access to additional documentation and test builds from Microsoft. The goal, Nash said, is not just to increase adoption for Windows 7-specific features such as Device Stage and multitouch, but also to convince developers to start building on some of the features that have been in place since Vista.
"Some features in Windows Vista...have not gotten the adoption we would like to see," Nash said, pointing in particular to the Windows Presentation Foundation graphics layer that was built into Vista, but has yet to be widely adopted as part of Windows applications.
During her years at CNET News, Ina Fried has changed beats several times, changed genders once, and covered both of the Pirates of Silicon Valley. These days, most of her attention is focused on Microsoft. E-mail Ina. 





Well yea, that's because WPF requires you to convert your application to .NET. I don't know many ISVs out there who want to retool their application to something so radically different; even if they were willing, it would be a major undertaking to go from a C++ application designed to use Win32 & GDI/GDI+ to .NET & WPF.
Way to limit your user base and sales!!!!
WPF is part of .Net 3.0 (and up), and is available on Windows XP.
So my my question is: If you didn't like Vista, are you really going to like Windows 7?
Just because its pasta doesn't mean it's going to be bad everywhere.
You can't assume that Windows 7 is going to be JUST LIKE Vista until it's here. I think theres enough to show so far that it isn't going to have the press of Vista.
Anyay, bad Vista taste is going to have to remain for folks upgrading to 7.
As for the upgrade option, I haven't seen the requirements so you may be right. It may require vista for the upgrade path. I can see this as fair. I would hope MS provides the upgrade option either free or for a rediculously low price, if it applies only to vista.
Is Steven Stephonofski F'n mad!??!! They have a full blown kick ass graphics programming framework at their disposal to write their fancy little ribbon UI in and they choose XSLT? If this isn't politics, I don't know what is. Sure, version 3.0 had performance issues but now that we're at 3.5 SP1, the framework actually beats native C++ graphics in most areas. This is where MS is pushing candy they won't even eat.
I don't know where you came up with XSLT - it uses XML mark-up for the view and it provides a win32 API for the behavior.
It isn't using WPF because that would require every win32 application to be ported to .NET whereas they are providing the ribbon to all the different frameworks (WPF - 2009), MFC - Visual Studio 2008 sp1, Native - Windows 7 and Vista.
Look at the General Format of XML Markup Files here:
http://msdn.microsoft.com/en-us/library/aa434075.aspx
That's interesting, they're using XAML with native code. Sweet!!! Is the native code library similar to what's there in WPF? That would rawk. Thanks for giving me some insight.
The hardware is more than powerful enough to run graphics. It's more than capable of doing any modern task with power to spare. It's the software that isn't being designed to take full advantage of the hardware. The software needs to change.
It's easy to criticize a company and not always easy to suggest feasible fixes, but Tantillo points out that Microsoft is out of touch with its Target Market. Apple has a lot of hype surrounding the release of its product in large part because they are delivering products that are Of Interest to their Target Market to begin with. They don't need to generate any sort of artificial demand; rather, their marketing (as good marketing should be) is a means of communicating with their Target Market. Microsoft, on the other hand, joined a dominant position in the market for a long time "and because of the way it evolved, the company does not have real marketing in its bones."
Full post: http://blog.marketingdoctor.tv/2009/01/24/brand-winners-and-losers-apple-and-microsoft.aspx
Plus, it's portability to silverlight is awesome. Most of what you can do in WPF you can do in silverlight.
You do have to stop thinking of it like windows forms because it's NOT the same. Most developers making the transition struggle with that.
do you honestly think it's going to be useful ?
keyboard/mouse will never be replaced by multi-touch
Multi-touch is for small screens like phones etc
maybe it can be of some use in netbooks but i highly doubt it !
try using it for 5 mins and come back to me on that
- by stumiller February 3, 2009 10:38 AM PST
- runs like a dream on my Mac Mini !
- Like this Reply to this comment
-
(32 Comments)