Did the Netbook Improve Windows 7's Performance?

Arnie87 writes "One Microsoft Way has an interesting article suggesting that the reason Microsoft is focusing so much on speed with Windows 7 is the whopping sales of netbooks. The article concludes by saying: 'If you plan on adopting Windows 7, you have the netbook to be thankful for, because Vista's successor would be a very different beast if Microsoft had less motivation to pursue performance.'"

Comments

Or maybe you're pulling that from your ass

[BadAnalogyGuy]

Face it, the real reason that Windows 7 is leaner than Vista is that Vista was a market flop because it tried to do all sorts of things that Windows users were simply not ready for.

There is nothing seriously wrong with Vista, and Windows 7 is mostly an optimized version 2 of Vista. So it's no surprise that with the codebase stabilized in Vista SP1 that Windows 7 will be able to build successfully upon that.

Re:Or maybe you're pulling that from your ass

[Anonymous Coward]

Face it, the real reason that Windows 7 is leaner than Vista is that Vista was a market flop because it tried to do all sorts of things that Windows users were simply not ready for.

Such as force users to give up applications that ran perfectly fine under previous versions of Windows.

Re:Or maybe you're pulling that from your ass

[rtb61]

My guess is this will be more of 'ready for Vista' underpowered desktop, now just in windows 'craps' (what version is it anyhow, up near 13 by now) for netbooks. Sure it will run windows, just barely, but run any applications on top and you'll get to re-experience that whole vista feeling all over again.

Personally I want my netbook to come basically complete with all the applications I will ever need at a very 'competitive' price, so when I drop it, drown it or some one pilfers it, I can just buy another one restore the data, not have to futz around with re-installing software or paying for B$ software licences bound to dead or missing hardware.

Netbooks are going to suffer a pretty hard life and the last thing you want to get caught up in, is buying the same software over and over again and you certainly don't want to end up paying three times the price in software versus what you are spending on hardware.

Re:Or maybe you're pulling that from your ass

[koro666]

Such as force users to give up applications that ran perfectly fine under previous versions of Windows.

They ran perfectly fine because Windows let them get away with whatever dirty tricks they were doing — which wasn't the case with Vista anymore.

Give me an application that is coded correctly and that does not try to be "more clever" than the operating system by using undocumented structures, functions, registry keys or whatever else, and I'll show you an application that runs fine on Vista.

Re:Or maybe you're pulling that from your ass

[Anonymous Coward]

There are lot of problems with portable applications which try to write into the directory where .exe file is installed.

Do portable progs on your fav linux distro do the same? That is, they write their configuration files to /bin or /usr/bin or /usr/local/bin or whatever.

What happens when an app with no root priviledge tries to write its configuration files in /bin? It fails spectacularly of course.

I don't like vista but isn't this double standard?

 

Re:Or maybe you're pulling that from your ass

[Minupla]

Speaking as an IT manager, I'll be dancing in the street the day that the last app stops this.

If I had a penny for every time a user lost data because some app decided to be clever in the manner mentioned above and not save it in the users profile directory...

Truly, if you were writing a linux app would you expect this to work? It's the same thing. Your app needs to expect that it can write to the user's home directory and temp locations. Fini. Done. Need to write somewhere else, make sure you set up the proper permissions during install time, when you'll be running with privs to access those directories.

Then I know where the user's data will be and can plan backups accordingly, without playing scavenger hunt with however many hundreds of apps my users are using.

Min

Re:Or maybe you're pulling that from your ass

[MrNaz]

I fully agree.

For years we (the FOSS community) have been bemoaning Windows' poor, totally broken security model. Now, when MS attempts to fix that and inevitably breaks applications that rely on the previous totally broken security model, we want to whine and moan about backwards compatibility?

Are we going to whine the same way if IE8 standardizes but breaks web pages that rely on IE7/IE6?

Seriously, there are some among us that simply will not be satisfied, and they are making the whole FOSS community look like a bunch of children.

Re:Or maybe you're pulling that from your ass

[the_womble]

What makes you think that the people complaining about backwards compatibility are the same people who complained about the Windows security model?

Re:Or maybe you're pulling that from your ass

[westlake]

By optimized you mean they have DRM turned off. Expect DRM to be in place for the final release candidate.

Let's put an end to this nonsense, shall we.

The Windows netbook has an Atom CPU, 1 GB of Ram and a 160 GB HDD. These specs are good and they going to get better. Much better.
The performance "hit" in managing DRM - the trusted path - whatever you chose to call it - isn't worth worrying about.

But if you want shelf space at WalMart, your product must deliver licensed media play out of the box.

Re:Or maybe you're pulling that from your ass

[LingNoi]

Then you do what Mozilla does and put it in this-feature-mozilla so when the standard does come along you don't screw up the web with your unstandardised features.

MS breaks standards because, GASP, there is a business case to do so

Yeah, ruining the web for everyone who's not using IE.

Re:Or maybe you're pulling that from your ass

[Blakey Rat]

The thing you have to realize is that most of the people who gripe about how lousy Windows is (or any Microsoft product) never actually use Windows. Or, alternatively, they haven't used Windows since Windows 98 and somehow think that it hasn't changed at all in a decade.

These are the people who complain about "constant bluescreens" in 2000, XP, Vista. The same type of people who don't realize that Windows has *two* CLI environments, one of which is admittedly quite poor (but only intended for backwards compatibility), and one of which is far superior to bash. And, over a year after IE7 added tabs to IE, I kept seeing posts on Slashdot saying that Firefox was a superior browser because it had tabs and IE didn't.

It's not just time, though. They also gripe about tools they don't use. For example, geeks here who rarely, if ever, use an office suite will go to great lengths to explain why the Office 2007 interface is far inferior to OpenOffice's interface. And frequently make statements like, "Office 97 had all the features anybody ever uses." They're not qualified to speak on this, of course, but they'll do it anyway.

In short, take everything you read here with huge grains of salt.

Win7 development started just after Vista shipped

[Anonymous Coward]

Yeah, because 3 years ago when Microsoft started the work that went into Windows 7 (remember MinWin?) they were smart enough to anticipate netbooks and so they did the performance work up front that would be necessary to make netbooks work well.

Or maybe, just maybe, they realized that Vista's performance sucked rocks and they decided to fix it and Netbooks were a happy beneficiary.

Bloat

[Ritz_Just_Ritz]

I dunno...Microsoft isn't the only faction that's suffered from some serious code bloat. Computers have gotten so much faster at such a rapid pace. Linux + Gnome and OSX have gotten rather porky as well....

I'd be happy to forego all the eye candy if it would speed up the work that I actually care about.

Best,

Re:Win7 development started just after Vista shipp

[haruchai]

I give credit to the OLPC and the push it gave to the computing world to come up with something lightweight but functional. And that was long before Vista shipped. The Netbooks were a result of the global awareness the OLPC gave to a need for cheap, portable, functional computing.

Maybe, Maybe not.

[Reed Solomon]

While they claim (and reports indicate) Windows 7 will be faster than Vista, I wouldn't put it past Microsoft to shoot themselves in the foot as soon as it's released.

And I don't think its the success of Netbooks that is making Microsoft focus on speed on netbooks. It's the fear of Linux/Android taking over where Windows Vista cannot work that is making them focus on speed for Windows 7. Amusingly enough, if Arm based netbooks take off, Not only is Microsoft screwed, but intel too.

Then again, Via Nano based netbooks are also starting to be rolled out, and they are comparable to the atom chipset. We'll see.

Nobody has made a netbook where when the lid is closed you have an e-ink screen for dual use as an ebook reader. This is totally pissing me off. I'm not the only person in the world who wants this or has thought of this.

Re:There is some bad news too

[wisty]

Even so, 10% is pretty damn good. Ask BMW, or Steve Jobs.

I'll agree - KDE is doing a lot of attractive stuff, with it's whole interoperability of user data focus. And the default theme looks better than Leopard.

I would have said the eeepc

[Anonymous Coward]

I never saw an OLPC here in Australia or anywhere else in my travels (including 2 trips to the US last year and 3 months in Europe).

I /did/ see a lot of eeePCs. Not all of them running Linux, but the day my parents came home with their shiny new eeePC running Linux, I thought to myself "Microsoft must be SHITTING BRICKS".

Re:Short answer - no

[D Ninja]

adding more people to the team will always be counterproductive since they'd only slow down the people who need to be 100% focused on finishing things up

Fixed that for you.

If there are any manager types reading this - THIS IS TRUE. More people does not make a project quicker to market. In fact, it has the reverse effect for a variety of reasons. A great book about this is The Mythical Man Month by Frederick P. Brooks. Please. Read. Do it for all of us techs-types who already know this.

thank the netbook?

[Ralph Spoilsport]

Yeah - godferbid they just make a quick efficient OS because it's a good idea...

Intense Rant: Don't fucking write it there

[kaiwai]

WARNING: Intense rant built up over years of raging against boy wonder dickhead programmers who think they're top shit.

Here is a great hint for all those boy wonders who write shit applications that spray their shit applications everywhere - fix your damn applications up.

It pisses me off when I see vendors spray DLL's everywhere, from their own directory to the Windows directory to the user directory and everything in between.

1) Keep your fucking application exe and all the bundled DLL's in your application director - leave the fucking Windows directory alone. It is not for YOU to place YOUR shit into. It is for Windows and Windows only.

2) Don't write shit to your application directory; if it is a universal setting then you should ask the user for permission and write it to the global registry. Is it a user related setting then save it to the user profile. No if's, no buts.

3) Don't use undocumented API's and hacks. You aren't cool, you aren't hip, it doesn't make you gods gift to the world because you're using private API calls never intended by Microsoft to be used outside their operating system development teams. Its private for a reason - private meaning it is not for you to fucking use. Hack away at Microsoft's private api's and I'll hack away at your privates.

Do the fucking job properly the first fucking time and stop turning a clean and pristine Windows installation ito a fucking dogs breakfast because you think you're top shit when clearly you're not.

Re:Intense Rant: Don't fucking write it there

[Khyber]

That's all well and nice, but there's one problem with that.

I'm just your average user, not a developer. Intuitively, when something is saved, especially something like a game save, I EXPECT it to be written to the game's fucking application directory.

Your sense of organization clashes with common sense, however I do agree with forbidding the assholes to write to system/system32 and other system-critical directories and spewing DLLs all over the place.

Re:Intense Rant: Don't fucking write it there

[tepples]

I'm just your average user, not a developer. Intuitively, when something is saved, especially something like a game save, I EXPECT it to be written to the game's fucking application directory.

Why? What's wrong with saving it inside C:\Documents and Settings\pino\Application Data\SomeCompany\SomeTitle\SavedGames\? That can be backed up with the rest of your home dir^W^W user profile, and it doesn't interfere with the saved games of other users on the same PC.

There is no 'we'

[mcrbids]

Wonder why 'we' are never happy here on slashdot? Why no matter what MicroSoft does, they are vilified by 'we'?

Here's a hint: take your user Id, and subtract 1. That's about how many DIFFERENT people registered here before yoi did. Each with their own ideas about priority and values, and what to lambaste MS for.

I lambaste them for lame things like email not working right with IMAP4 servers in WinMobile 5, 6, 6.1, and 6.5. That's 3 YEARS that some as simple as deleting an email hasn't worked right in a device primarily bought to (ahem) read email.