Windows 7 is gonna be the name!

Today the name for the next version of Microsoft Windows is announced! And the name is….Windows 7! Microsoft’s Mike Nash announced the new name earlier today (or was it yesterday?) on the Windows Vista blog.

And, as you probably know, since we began development of the next version of the Windows client operating system we have been referring to it by a codename, “Windows 7.”  But now is a good time to announce that we’ve decided to officially call the next version of Windows, “Windows 7.”

While I know there have been a few cases at Microsoft when the codename of a product was used for the final release, I am pretty sure that this is a first for Windows. You might wonder about the decision.

The decision to use the name Windows 7 is about simplicity. Over the years, we have taken different approaches to naming Windows.  We’ve used version numbers like Windows 3.11, or dates like Windows 98, or “aspirational” monikers like Windows XP or Windows Vista.  And since we do not ship new versions of Windows every year, using a date did not make sense.  Likewise, coming up with an all-new “aspirational” name does not do justice to what we are trying to achieve, which is to stay firmly rooted in our aspirations for Windows Vista, while evolving and refining the substantial investments in platform technology in Windows Vista into the next generation of Windows.

Simply put, this is the seventh release of Windows, so therefore “Windows 7” just makes sense.

So now it’s just waiting till the first alpha’s and beta’s will be released!

Windows ‘7’ and the Future of Wireless networking

Windows 7

On iStartedSomething I read the following : It’s rare for a week to go by without a few interesting Microsoft job advertisements. One of which posted last week provides a pretty good idea at how the next version of Windows will improve the wireless networking experience.

Vista was about making Wi-Fi connections as seamless, manageable and secure as wired networks.

The next Windows version is really about taking Wireless networking to the next level by enabling new complete end to end scenarios and experiences that are going to change how windows PCs interact with each other and other devices and nodes over a wireless network.

As a part of the Windows Networking Ecosystem Technologies team, you will be working on scenarios around virtualizing Wireless to allow connections to multiple networks simultaneously. You will be working on enabling new windows to windows connectivity paths within a wireless network to improve wireless throughput and latency. You will be working on wireless-only office and mesh networking scenarios that will make setup and management of wireless networks quick and inexpensive with the goal to reduce TCO for centrally controlled and secured deployments by improving manageability, performance and reliability.

As a part of this work, you will be working closely on existing and in-works wireless standards such as IEEE 802.11s, 802.11k, 802.11r, 802.11w. This position will provide you the unique opportunity of working on core wireless areas as well as collaborating with several other key Windows technologies to deliver a complete functional end to end scenario. The work will be in both the Windows kernel and user space.

Whilst wireless meshing is an exciting feature to look forward to, I think the killer feature will be virtualizing wireless adapters. Currently, one wireless adapter can only connect to one wireless network. Connecting to many networks simultaneously could open up a range of opportunities beyond just performance enhancements.

For example, if you were to set up an ad-hoc computer-to-computer connection right now, you’d have to give up your current infrastructure (computer-to-router) connection. That means you’ll most likely lost internet connection as both users are only connected to each other. With virtualized adapters, you would be able to allocate one to your ad-hoc network, and another to keep your existing connection.

That together with wireless meshing technology, this could eliminate wireless dead-spots altogether. Because each wireless client could also become a repeater for the wireless signal (ad-hoc), like ripples in a pond the wireless signal will expand as long as users are within range of each other even if they’re well outside the original access point’s range.