Linked by Thom Holwerda on Fri 12th Dec 2008 23:44 UTC, submitted by google_ninja
I'm sure you're all still (sadly) familiar with the recent 'debate' I had with InfoWorld's Randall Kennedy, which detailed a lot of silly things. The seed of that discussion was planted with Kennedy's first article which, among other things, claimed that Windows 7 performed similarly to Windows Vista (meaning, slower than XP). Leaving the thread count discussion behind, Kennedy did include a benchmark which showed that Windows 7 performed similar to Windows Vista. There's a new benchmark out now, comparing a slightly more recent build of Windows 7 to Vista RTM/SP1 and XP SP3, and in these tests, Windows 7 blows all of those out of the water.
Thread beginning with comment 340309
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-03-18
"Just blaming developers is far too easy."
It's where the blame lies. MS provides simple and easy methods for installing and running apps that do not need Administrative rights. If developers can't figure out how to use them, it's not Microsoft's fault.
" As a software architect, I can assure you that developers are not joyfully going to restrict their own apps with installation requirement like "Admin Rights Needed": There are normally good reasons for harming the field of application of your own app (spending 20% of your time / budget or so just to make the software run under restrictions is a good reason, believe it or not!)."
I have no idea what you are saying "There are normally good reasons for harming the field of application of your own app" doesn't make any sense.
"I knew of a case where "no apparent reason" was the dependency on a certain MS system DLL (needed because of bugs in other versions)."
You don't need Admin rights to load a DLL.
"I guess that MS (once again) harmed one of the golden rules of software framework APIs "Make simple things simple and hard things possible" (developing for restricted accounts should be "simple" but seems to be so "hard" that developers don't do it unless forced to)."
Most of the problem is the result of installing in privileged locations, or writing files/registry settings to privileged locations. Are you telling me that changing a few file paths and registry locations is just to difficult for the average developer? If so - what do you suggest MS do to correct the problem?
"And talking about sloppy programming: Just have a look at a default Windows installation (preferably a non-English one) to see what sloppy programming means. It's not that MS itself is a good example"
Guess I will just have to take your word for that - have no idea what it has to do with the topic at hand.