Windows 8 starts to come into focus
Summary: I get questions periodically about whether Windows 7 marks the end of the Microsoft operating system road. The short answer is no. And there are two new Microsoft job postings for Windows 8 to prove it to the doubters.
I get questions periodically about whether Windows 7 marks the end of the Microsoft operating system road.
Some users wonder whether will Microsoft's next version of Windows be completely cloud-based? Will it be Midori with the Windows name slapped on it?
No and no. The bottom line: Windows isn't done when Windows 7 is released to manufacturing (most likely in late fall 2009). Windows 8 has been on the drawing board/planning stages for a while now. And as the "Codename Windows" blog recently reported, Microsoft is starting to hire developers specifically for Windows 8.
Codename Windows highlighted last week a Microsoft job posting from April 14, seeking someone to help with the next generation of the Distributed File System Replication (DFSR) storage technology inside the next version of Windows:
"For the upcoming version of Windows, new critical features are being worked on including cluster support and support for one way replication. The core engine is also being reworked to provide dramatic performance improvements. We will also soon be starting major improvements for Windows 8 where we will be including innovative features which will revolutionize file access in branch offices."
There's another Windows 8 job posting from April 16 that focuses on Windows 8 Server (a k a Windows Server 2011 or whatever it ends up being called). It's for another job focused on the Windows file system:
"In Windows Server 2008 R2 release, the Server UX Test team (under the File Server Management organization) is finalizing the MMC [Microsoft Management Console] based User eXperience (UX)/Interfaces for the File Server Role. Currently the team owns DFS [Distributed File System] Management, Share and Storage Management, FSRM [File Server Resource Manager] & Classification UI, Disk Management, SMFS. For Windows 8, the SSD organization is working on the next version of the file server.
"As the team moved to Windows 8, you will have 2 main responsibilities - (i) put on the customer/design critique hat as we plan our next version file server management experience (i) participating in the architectural design, and development and driving automated testing for managing the next generation file server. Our current automation does not meet the multi-machine paradigm requirement and so you will contribute significantly in the development of test automation to validate setup/configuration of the new server, managing configuration changes, performing diagnostics and reporting using Power Shell, Command line, Object Model, UI."
If Microsoft sticks to the kind of schedule to which it has adhered with Windows 7, Windows 8 will be released around 2011 (with Microsoft publicly promising a 2012 delivery target). While it's way too early to speculate what kinds of features will be in it, it definitely is in the works....
Any early requests for features/functionality you're hoping makes it into Windows 8 client and server?
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Sheesh Let The Dust Settle From Windows 7
They don't want it to.
Who really needs an OS per se?
Umm... no.
OS/BIOS boundries merging
Actually - the BIOS is going away.
The BIOS these days really does little more than tell the OS what hardware exists and provides a UI to configure the hardware.
Perhaps you're confusing BIOS with Kernel?
What I'm saying is.....
Actually, There is Coreboot.........
No Mac is an EFI boot sequence and maybe ados is going away.
actually its evolving
the flash memory, with some instant on options,
granted this is not a BIOS by the definition of
the acronym B.I.O.S. but it evolved out of more
advanced BIOS setups, I don't think it will be
many more generations before instant on systems
are standard.
You need the BIOS at power-up.
Back in the day, once DOS was loaded, it used the BIOS to talk to the devices connect to the computer. Later versions of DOS could load devices drivers to talk to hardware connected to the computer but not known to the BIOS and thus not accessible until after DOS was loaded and running.
With the introduction of premptive multitasking in Windows NT 3.x (1993), the BIOS was no longer sufficent to meed the needs of Windows. The exception was as a path to support legacy software which was still dependent upon direct access to the BIOS.
Those days are long gone. The BIOS remains important but only for access to hardware at boot time.
While dedicated "appliance-like" devices like cell phones, place their operating system directly into firmware - effectively making the BIOS into a full-fledged OS - doing so removes a lot of flexibility so don't expect the BIOS to go away altogether in generic computing devices.
I think they meant...
I understand the argument that many make. If you look at whats done by your average computer user...how much of it can you really say depends on any specific OS?
You don't build a special OS for your minimal clients....
For one thing, you're making a HUGE assumption about what the 'average user' uses. It looks simple at the top, but like an iceberg, it's just the visible tip.
Oh, you mean like...
yea and most of that I can do on my phone...
most everything I do on my computer I can't do
on my phone, and won't run on linux or mac
without virtualization which will slow it down
too much anyways... so... not yet. OS is still
relevant... I don't see and end soon.
Umm... yes, actually.
Umm, I don't think you got what he meant...
He said the OS was irrelevant in the fact that they all pretty much do the same these days.
But good job trying to look smart listing every OS you could find on google..
You're kidding, right?
And as soon as you want to so anything complex you either end up writing your own libraries (Hello 1985) or you end up with a hodgepodge of inconsistent apps that have zero interoperability.
As for 'this internet age'... the transport may be TCP/IP (and typically provided by the OS), but the user experience is OS.
Unless you're seriously proposing there be one IM client, one spreadsheet... one of everything, your suggestion condemns developers to spend a HUGE amount of time reinventing the wheel over and over - or licensing it from someone else.
How exactly is this *better*?
And what would we...
Linux is great, because of it's NON-genericness, I think "Windows" has BECOME the Generic operating system!
Of course, if this ever does go into effect, I wonder if Negroponte would be interested in the project?
User experience is the OS??