Linked by on Tue 27th May 2008 15:00 UTC
Windows So far, Microsoft has been very tight-lipped about Windows 7, carefully trying to prevent another Longhorn PR disaster where the company promised the heavens and more for Longhorn, but in the end ditched Longhorn to make way for Vista. Chris Flores (Windows Client Communications Team) as well as Steven Sinofsky, has broken the silence a little bit to talk about Windows 7. In addition, it is believed Windows 7 will make its first official debut at the D6 All Things Digital conference today, during a keynote held by Steve Ballmer and Bill Gates.
Permalink for comment 315801
To read all comments associated with this story, please click here.
RE[2]: Another Missed Opportunity
by phoehne on Tue 27th May 2008 17:43 UTC in reply to "RE: Another Missed Opportunity"
Member since:

Okay, you're clueless. What's not working with the Windows kernel is that it does require massive amounts of memory to run the basic O/S. In fact, a recent posting (can't find it right now) about an Intel engineer that benchmarked various tasks under different versions of Windows and Office found they were slower on Vista (on modern hardware) than on Windows 2000 on old hardware. That's right. You're upgrading to Vista to actually run slower on brand-spanking new hardware.

Windows suffers from another problem, which is 20+ years of cruft. Last time I was coding on Windows there were 3 different C API's for memory management. Only one was current but all three were supported so code going back to Windows 3.1 had a shot of running. It's time Microsoft dumped some of those API's the way Apple did with the Carbon migration prior to OS X. Why dump those old API's? Because they lock in old, out-dated concepts and practices, which can interfere with new kernel development. Even if they're just wrappers around the new API's, they should go the way of the do-do.

As recently as early releases of XP there are way too many reports of user programs causing kernel crashes. (And no, I'm not talking about buggy device drivers). These are instances of user programs passing bad parameters back to the Win32 functions causing Windows to BSOD. That should happen 0 times.

I've written software on Windows at various stages in my career since Windows NT 4 so that people can run businesses and make money. I've had the dubious pleasure of writing OCX and Active X controls, COM+ components, all the way through .NET GUI's. What was modern in the Windows NT 4 sense (circa 1997) is now no longer modern. It needs a facelift. It needs a cleanup. It needs to live well in a reasonable environment. It needs that because otherwise it becomes increasingly a dead weight instead of a useful tool.

Windows is not the best kernel available by any stretch of the imagination. For one thing, it lacks real time capabilities (which Windows CE ironically provides). The thread scheduler is counter intuitive. The filesystem is slow (especially over network shares). The part I especially love is the random waiting while network browsing returns information about computers, printers and networks. Windows isn't evil. It does need work. It would be nice to see Microsoft stop dicking around with Yahoo or Zune and focus on it's core competency, Operating Systems before it begins to look like it's core incompetency.

Edited 2008-05-27 17:50 UTC

Reply Parent Score: 14