...we re-plumbed the graphics infrastructure for Windows. That has a huge number of benefits for the ecosystem at large. It means the drivers can be made more robust, they don't have to run in kernel mode and things like that. But we also didn't execute on that as flawlessly as I think we all would have liked collectively as the ecosystem. The team worked super hard with the partners in graphics to really do a great job, but the schedule challenges that we had, and the information disclosure weren't consistent with the realities of the project, which made it all a much trickier end point when we got to the general availability in January.
So, were the problems with Vista support and Vista enthusiasm — it sounds like you're saying they were mostly issues of disclosure as opposed to execution on the product. Is that right?
Sinofsky: I don't really want to dwell too much on the views of the past, and sort of just tell you again the lessons that we learned in working with partners. The team feels this tremendous responsibility to working with IHVs and ISVs and OEMs (original equipment manufacturers), because they're running businesses, they have their own business challenges, their own business goals, their own aspirations, and when we speak about what we might do, they will take it seriously. So, we appreciate that and we respect that, and it's a great benefit. But if we're not accurate or the information we provide causes them to do one thing, and then we change our mind, that doesn't bring the ecosystem forward. A big set of challenges that we learned...is making sure that the information we provide legitimately reflects the promises that we're making to ourselves and to the team as a product.
I know you said you don't really want to look back, so maybe looking forward a little bit...We haven't heard a lot about Windows 7, but we've heard about a couple of things discussed. The real areas I've heard a lot about are this idea of a new kernel, a minimum Windows kernel that came up in a speech, and then some stuff around new user interfaces. Can you tell us a little bit more about where those things fit in with how you guys are thinking about Windows 7?
Sinofsky: We're very clear that drivers and software that work on Windows Vista are going to work really well on Windows 7; in fact, they'll work the same. We're going to not introduce additional compatibilities, particularly in the driver model. Windows Vista was about improving those things. We are going to build on the success and the strength of the Windows Server 2008 kernel, and that has all of this work that you've been talking about. The key there is that the kernel in Windows Server 08 is an evolution of the kernel in Windows Vista, and then Windows 7 will be a further evolution of that kernel as well.
So, memory management, networking, process management, all of the security hardening, all of those things will carry forth, and maintain the compatibility with applications that people expect. Finally, we are going to make sure that the release is available both in 32 bit and 64 bit, which is an additional help for maintaining compatibility, particularly with device drivers. As the 64-bit ecosystem catches up, we expect more and more people, particularly enthusiasts, to be running 64 bit. For many people that's a great scenario today. I know I run 64 bit on most of my machines, including my primary laptop.
What was this idea then that got talked about in terms of a kind of minimum kernel?
Sinofsky: Well, why don't we stick at a higher level today, because I think that I don't want to really dive into the implementation details today.
Where do you see the biggest opportunities for the OS to matter in the coming years? One area might be new user interfaces, but people talk a lot about the browser making the OS less important. I know that's generally not a view that Microsoft holds, and usually not at all a view the Windows unit holds. So what are the ways that the OS can continue to matter?
Sinofsky: There will be a lot of features in Windows 7. It's a major release. I talked about the kernel and driver compatibility and (application) compatibility, but there is a lot more for us to talk about. We'll certainly be in touch.
Is one of the goals with Windows 7 that there will be more things right out of the box to get people interested in this release?
Sinofsky: Again I don't want to talk about any more specifics today, because we're focused today on how we're going to communicate things. But really again to really make sure I'm clear, we're working on a major release, and I think that each customer segment will have its own way of understanding what it means for them to be a significant release. And some of the things that we're going to do are going to make the release more applicable to a broader set of people, but it also might mean, oh, well, if you're not re-architecting the whole thing, then maybe it's not a major release. But we're actually going to bring forward the compatibility, and we're going to make sure that there's a lot of value for everybody who's a customer of Windows 7.
Are there any sorts of things that are happening in the overall PC world that are influencing how you guys are designing the operating system? I would imagine one of the things that certainly would influence it would be the sort of extensions to Vista, the Windows Live services. How important are online service extensions to the operating system going forward?
Sinofsky: The great thing about the Windows and PC ecosystem is that there's no shortage of activity in every dimension. Right now, today, we're really focused on just making sure everybody understands how we're going to talk about all of the things that we're going to do in this next release of Windows, but what we really want to do is kind of stay focused on that, and let us do a good job making sure that the things we are working on are really going to be great for each of the different kinds of customers of the product.
I think somebody that reads this conversation we're having is probably going to walk away again with an impression that I know you don't always like: that the Windows team is really being closed and isolated. I know one of the points you want to make is that you guys are talking to your partners. Is there more you would say about why is it important to be so selective about what gets shared ahead of time?
Sinofsky: So, everybody wants to know sooner than later what we're doing. And what we're always trying to balance is, well, if we make mistakes, then that has repercussions in the ecosystem that we don't really want to have, and we really want to be a responsible team as part of the overall ecosystem. If folks need an example, the best example that I could offer in terms of really trying to be respectful of the needs of the marketplace is really what we've been doing with Internet Explorer. I feel like we really worked on a great plan. The people who helped us to design how we were going to be compatible, how we were going to be compliant, the standard support that we did, were all part of the development process early on, all the outside parties.
Then we turned around and said, "OK, now we're ready to go to developers." We had a conference at Mix, and we talked about the development opportunities in Internet Explorer, because they were actionable. We gave people the code, we had published the specifications, we were ready to go not just for them to go do the work but for them to give us the feedback, and we were in a position to really act on it. That's really what we're trying to do with the next release of Windows as well.
I can understand why it's too early to talk about specific features in 7, but I'm a little surprised that it's too early to talk about some of your philosophies about where Windows has an opportunity to grow, and how things are changing, and some of those things, some of the factors that are influencing your work.
Sinofsky: Well, again I think what I would say is that we're talking about different types of customers, and different types of customers have different needs for information and are able to absorb it in a way that I think is mutually responsible.
If I'm understanding correctly, the things that you guys are ready to say about Windows 7 is it will be in 32- and 64-bit flavors, and the idea is that 64 bit will grow over time, although it's still kind of an enthusiast thing.
Sinofsky: Well, I didn't say it's still kind of an enthusiast thing; I did say I expect for sure our enthusiasts will be running it. It's actually professional graphics people who use it, industrial design uses it. There are a lot of segments that are very active in using it.
Do you think that 64 bit has come along slower than people would have thought?
Sinofsky: A lot of drivers haven't been written yet, and we expect that they're available now with new hardware, and we expect that that library will be built up over time.
Then the other thing that seemed like you were saying about 7 is that it will really focus on the underpinnings that are in Vista and Windows Server 2008, and so people should expect new features but not necessarily a lot of under-the-hood changes that require significant testing and so forth. Is that correct?
Sinofsky: I didn't actually say that. What I did say (is) that Windows Vista established a very solid foundation, a multiyear foundation, particularly on subsystems like graphics and audio and storage and things like that, and Windows 7--and then Windows Server 2008 built on that foundation, and Windows 7 will continue to build on that foundation as well.
You mentioned Windows Server 2008 being kind of the core on top of which you've built. Does that mean it gets some of the benefits of the modular architecture that the Server 08 release had, where you had this notion of a Windows Core configuration of Windows Server, and then you can sort of add pieces on top of that when they're needed?
Sinofsky: I think we've talked enough about the direction that we're heading with the specifics of the product today, since we really did want to focus a little bit more on just talking about how we're communicating with partners and customers and the ecosystem at large.
Do you think there's a risk that the more tight-lipped nature publicly will alienate some enthusiasts and folks who really want to know early on where you guys are going?
Sinofsky: There are many different models for disclosure that different companies work in, and I talked about the one that we're basing on the lessons that we learned from Windows Vista. But, of course, you could look at any of the other vendors in the marketplace, and see how they deal with disclosure, and come up with different models, and speculate about the pros and cons that they really see. I think that we're just focused — the No. 1 goal we're focused on is really the responsibility that we feel, and the respect that we have for all of our customers and partners, and making sure that what we share with them is really accurate and actionable, and that we are focused, like I keep saying, promise and deliver.
Let me just end with this. Look, we're working — the team is working super, super hard on this release of Windows, and you have to imagine we'd really be excited to start showing it to people. We want to show it, and we want people to get their hands on it, but we want to do that under the umbrella of being responsible members of the ecosystem, and being respectful of people's time and energy and the work that they'll put in to making Windows 7 great from the work that they can do.
So, why don't we say we're on target for the three years after general availability [of Vista], we're very excited about the release that we have, and we're very focused on promising and delivering.
Is it just me all did that really didn't tell us anything at all? I just spent 5 mins reading some guy going around in a full circle.