Engineers Tell How Feedback Shaped Windows 7
An anonymous reader writes "Ars Technica took the time to talk to three members of the Windows 7 product development and planning team to find out how user feedback impacted the latest version of Windows. There's some market speak you'll have to wade through, but overall it gives a solid picture regarding the development of a Windows release."
is not an engineer. Windows 7 requires lots more RAM than XP and is slower than XP on the same hardware. That doesn't speak highly about those who engineered Windows 7.
In every other field, progress mans efficiency, not more bloat.
If you keep throwing chairs, one day you'll break windows....
Wow, how did MS pay you to write that? When I talked about % ratings i was referring to IE's compliance in working with CSS (using the acid test). Every single time I create a style sheet I have use stupid hacks to make a site look acceptable on IE. I never have this problem in Safari, firefox (sometimes), but with IE it's a gamble between what you expect the code to do and it actually does. So I wasn't being a troll. Just ask any web developer what they think of IE - we hate it.
Yeah, because Windows Server is a minority actor in the corporate/enterprise space. I assume that's the "point" you're trying to make?
You've been developing operating systems for 30 years. It took you this long to realize that different users have different needs, and that your OS should run on low-end hardware?
The Windows OS typically enters the consumer market as an attractive upgrade for the shopper eying the OEM system bundle.
The HP at WalMart which ships with the 64 bit OS, the quad core CPU, 8 GB RAM, the 1 TB HDD, the Blu-Ray capable video card with HDMI output and so on.
Mid-line this year, will be entry level this year or the next - and at mid-line the CPU has become an i-something with 12 GB RAM.
When you hit the ground running, you can keep on going for years.
The geek is obsessed with the low-end.
But when the XP Atom netbook with much better specs entered the market, it wiped the floor with Linux.
It cleared the space for Win 7 - and the geek never saw it coming.
When it comes to tail dragging, m$ sets the world standard. When one considers such standards as HTML 4.1/5.0, IEx was not there first; yet m$ could easily be. When it comes to XML, XSLT, Javascript, SVG, and CSS; IEx lags. And why should m$ care? They already have your money. But lets also consider AJAX, XmlHttpRequest is a Petri Dish for malwarz to fester in. And why does anyone need XmlHttpRequest? A HTML Form sends a request to your server. You're web service generates an XML string, all one needs to do is insert an XML prepossessor statement for a XSLT file,( place the XSLT entry at line 2), the Browser does the rest. Lets talk Browser world usages, IEx is at 67 to 33, it use to be 98 to 2. Of the 5 major browsers used on the planet today, it's IEx that one has to spend extra money on for development because IEx can't figure out how to have IEx do it to W3C standards. What's m$ solution? Corrupt the world body by buying off people; this is public record, and it's NOT good Engineering.