ZAVibes

NetworkWorld got their hands on Microsoft’s latest addition to the server OS market and had a chance to poke around inside Windows Server 2008. It seems that the new release is a vast improvement over older versions in both security and performance but still lacking in several key areas.
“There’s even a minimalist installation called Windows Server Core that can run various server roles (such as DNS, DHCP, Active Directory components) but not applications (like SQL Server or IIS dynamic pages). It’s otherwise a scripted host system for headless operations. There’s no GUI front end to a Windows Server Core box, but it is managed by a command line interface (CLI), scripts, remotely via System Manager or other management applications that support Windows Management Instrumentation (WMI), or by Remote Terminal Services. It’s also a potential resource-slimmed substrate for Hyper-V and virtualization architectures.”

When Windows 7 launches sometime after the start of 2010, the desktop OS will be Microsoft’s most ‘modular’ operating system to date. That’s not necessarily a good thing, of course; Windows Vista is a sprawling, complex OS. From Microsoft’s perspective, though, there are many possible benefits. The OS’s developers can add/remove functionality module by module. New modules could be sold post-launch, keeping revenue streams strong. A modular approach could also allow the company to make functionality available on a time-limited basis, potentially allowing users to ‘rent’ a feature if it’s needed on a one-off basis. Microsoft is already testing ‘pay as you go’ consumer subscriptions in developing countries

Google Chrome and Internet Explorer 8 herald a new, resource-intensive era in Web browsing, one sure to shift our conception of acceptable minimum system requirements, InfoWorld’s Randall Kennedy concludes in his head-to-head comparison of the recently announced multi-process, tabbed browsers.

Whereas single-process browsers such as Firefox aim for lean, efficient browsing experiences, Chrome and IE 8 are all about delivering a robust platform for reliably running multiple Web apps in a tabbed format in answer to the Web’s evolving needs. To do this, Chrome takes a ‘purist’ approach, launching multiple, discrete processes to isolate and protect each tab’s contents. IE 8, on the other hand, goes hybrid, creating multiple instances of the iexplore.exe process without specifically assigning each tab to its own instance. ‘Google’s purist approach will ultimately prove more robust,’ Kennedy argues, ‘but at a cost in terms of resource consumption.’ At what cost? Kennedy’s comparison found Chrome ‘out-bloated’ IE 8, consuming an average of 267MB vs. IE 8’s 211MB. This, and recent indications that IE 8 itself consumes more resources than Vista, surely announce a new, very demanding era in Web-centric computing