posted on October 13, 2008 by Bryant Zadegan

Slashdot readers, thanks for visiting. Feel free to chime in here or on the forums.
Mike Nash, former Security Guru and current Client Guru over at Microsoft, has just announced on the Windows Vista Blog that the new name for Windows “7” will be:
…which makes me wonder why it’s going to be NT 6.1.
It also means that Windows Strata will likely be the codename for the new Cloud OS discussed by Ballmer earlier this month. We’ll carry more about all of this from PDC in two weeks.
Update: Brandon followed up with me on twitter saying it’s the 7th release of Windows, which is ridiculous:
- Windows
- Windows 2
- Windows 3.0
- Windows NT (NT 4)
- Windows 2000 (NT 5)
- Windows XP (NT 5.1)
- Windows Vista (NT 6)
That’s 7 releases right there, including XP. If XP isn’t counted because it’s Kernel 5.1 (which would bring the total with Windows 7 back down to seven), then why is Windows 7 being counted as the “seventh” release if it’s kernel 6.1? I hope I’m not the only one seeing the naming problem here.
Kernel increments are used mostly for application compatibility purposes, but still, the logic is lost upon us as most people would count XP as a semi-major release in comparison to 2000. I hope the guys at the Blog have an update, because this is weird.
More potential views of how this could have worked (Update 2: as well as Mike’s clarification) after the break.
Read More »
posted on June 15, 2008 by Chris Holmes
I can give a pretty interesting perspective on the Windows 7 leak, considering said perspective is coming from someone who has had this build for 3+ months as of the writing of this post.
Before I really jump in, I should explain why leaks of this magnitude are bad. Believe it or not, these leaks do hurt Microsoft and the dev process of the operating system, especially this early in the cycle. When a leak happens, Microsoft has to devote time to investigating the leak and trying to pin down a source, ultimately the internal source or OEM who leaked it. Leaks are also bad because there are just some things that aren’t ready to be seen outside of Redmond yet, especially by the average Joe user. Say a build leaks, and average Joe doesn’t like a certain feature, or even more realistic, finds a real nasty bug. He blogs about that and next thing you know everyone is jumping on the slingfest bandwagon and presto, bad image before the product is even out of the gate.
The main thing about the 6519 leak that gets me is the fact that it leaked after so much time. I can only assume that it came from someone in the group that got the build about a month ago, and for some reason was looking for a “15 minutes of fame” moment. There is, however, a silver lining to all of this. The build is hard coded to expire on June 6th, after which date the activation system will lock you out of the system. Why someone would leak after expiration, you ask? Well it’s actually a pretty simple answer. They get their little moment of fame and (they think) cause little damage to Microsoft since Joe user can’t use it on a daily basis. The fact is though, the beta community is rather unique, we take builds of OS’s and actually use them on our machines to tinker with and see the direction that Microsoft is going with the future of Windows. With 6519, running on the current date is now impossible, but the OS can be used if you set the date back before expiration, which some will probably be willing to do, just for bragging rights.
I guess the point I am trying to make with all of this is 6519 never should have been leaked, but it is the unfortunate fact that we have some people in this community that just can’t seem to keep anything under wraps and thinks that leaking a build will gain them some kind of celebrity status. That could not be more inaccurate. Within the last few years leakers have been looked upon as the black sheep in the community, for the exact reasons that I mentioned earlier. The fact is that these people will never learn, and will likely continue to do things like this.
posted on June 9, 2008 by Bryant Zadegan

Wired has an interesting article on how the iPhone boosted smartphone sales for other manufacturers (most notably RIM and Palm). With the next version of the iPhone now released, you might be asking yourself
- What will Microsoft do to keep Apple from breaking into the enterprise smartphone market?
- Why haven’t I bought this new iPhone yet?
- What’s that pretty thing in the Crystal Ball?
Now might be a good time to analyze the potential impact Apple’s iPhone might have on Windows Mobile.
Read More »