Windows 7 vs. Windows XP On a Netbook
Justin writes "Many in the industry are counting on Windows 7 to bring the netbook market to the next level. Having netbook manufacturers ship netbooks with 7+ year old Windows XP pre-installed surely deterred some from joining the ranks of households with the small, light and portable netbooks. It seems Microsoft has addressed most of the pitfalls of Windows Vista on a netbook by increasing battery life and performance to be very close to that of the lighter-weight Windows XP. Legit Reviews has the full scoop of battery life and performance tests pitting Windows 7 against Windows XP on the ASUS Eee PC 1005HA Netbook." I'd like to see a follow-up with a few different Netbook-friendly Linux distros, too.
I thought the point of netbooks was to have a computer for accessing the internet and that's about it. Last I checked, XP could access the internet. I don't see the point in putting Windows 7 on your netbook at all.
Doom 2 versus Quake 2 on a 386.
Comment removed based on user account deletion
Should have used the RTM that came out... the RC is months old... lots of stuff has changed
Let's see... a bunch of hardware benchmarks, which would be expected to result in negligible difference between different versions of Windows. Does Vista REALLY come out significantly worse than XP on these kinds of benchmarks?
How about something relevant to netbooks? What's the memory footprint? Disk footprint?
What a fracking joke! That the new product is almost as good as the 7 year old one that it replaces.
"It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
It might not be Ubuntu's fault, but it's Ubuntu's problem.
Do you honestly think that a stock install of Ubuntu 9.04 uses fewer CPU cycles than, say, Debian Woody? Hell, grab some floppies and fire up that old 286; with all the improvements to Linux over the years, new distros must run circles around the old ones we had back then!
Software becomes more complicated with each new version. Features get added. The UI gets improved. Security gets heightened. The fact the Microsoft managed to include all the new features of the past seven years without significantly increasing power consumption or decreasing performance is indeed an accomplishment.
Also, note the difference between performance and productivity. A GUI is a good example. A command line will always perform better than a GUI. It can run on even the lightest of hardware. But you can (usually) be more productive with a GUI than by typing long, obscure commands into a Bash terminal. Another example is the search indexer: It may be more work for your CPU and hard drive, but it saves you lots of time hunting for files or emails.
How can I believe you when you tell me what I don't want to hear?
It's about how well they run on these machines. It's ALL ABOUT the hardware!
Your comment is some retarded shit. RTFA
Yes, that's good, isn't it? A 7 year old OS vs. a not-yet-released OS running on current hardware... and the not-yet-released OS performs almost just as well as the 7 year old OS?
I'd say that's pretty good. Typical idea is that older OS's will run faster since they were smaller and HAD to run on .. less hardware. Hardware is better, so OS's can plan on using more of it. An OS that is able to run almost as well as a 7 year old OS on CURRENT hardware is doing pretty well.
"Security for starters. Vista changed a lot under the hood to improve security" - by wjousts (1529427) on Wednesday July 29, @03:02PM (#28871253)
Well... they did, AND THEY DIDN'T: Like what, you might ask?
1.) HOSTS files not being able to use 0 as a blocking IP address in a CUSTOM HOSTS FILE (for both added speed & security), vs. 0.0.0.0 or 127.0.0.1 (the "loopback adapter" being the WORST of the lot, in terms of efficiency & internal file read speed in loops to 'suck it in' to either the local DNS cache client OR the diskcache (which again, MS has a problem in the DNS Client of it 'breaking down' on LARGER hosts files (purely relative, iirc, when they go over the 4mb mark in size) & it should not be - it's like it is a static sized array/buffer, vs. a dynamic one, like the local diskcache uses, which "takes over" when you turn off the faulty DNS client).
AND
2.) WFP & NDIS6 (which I get into the former & why I think it's not as solid as the 3 part "zone defense"/"greek phalanx" of the older models of Windows for IPSEC.SYS, IPNAT.SYS, TCPIP.SYS, IPFLTDRV.SYS, & AFD.SYS, which acted like a zone defense/greek phalanx via 3 separate drivers, operating @ 3 DIFFERENT LEVELS of the IP stack (whereas it appears WFP only uses a single point layer defense, & when it's down? It's done for, which is NOT the case with the older model))...
3.) NDIS6 based firewalls... see my p.s. below, for that from ROOTKIT.COM
Lots more, & here are the details:
Windows 7, VISTA, & Server 2008 have a couple of "issues" I don't like in them, & you may not either, depending on your point of view (mine's based solely on efficiency & security), & if my take on these issues aren't "good enough"? I suggest reading what ROOTKIT.COM says, link URL is in my "p.s." @ the bottom of this post:
1.) HOSTS files being unable to use "0" for a blocking IP address - this started in 12/09/2008 after an "MS Patch Tuesday" in fact for VISTA (when it had NO problem using it before that, as Windows 2000/XP/Server 2003 still can)... & yes, this continues in its descendants, Windows Server 2008 &/or Windows 7 as well.
So, why is this a "problem" you might ask?
Ok - since you can technically use either:
a.) 127.0.0.1 (the "loopback adapter address")
b.) 0.0.0.0 (next smallest & next most efficient)
c.) The smallest & fastest plain-jane 0
PER EACH HOSTS FILE ENTRY/RECORD...
You can use ANY of those, in order to block out known bad sites &/or adbanners in a HOSTS file this way??
Microsoft has "promoted bloat" in doing so... no questions asked.
Simply because
1.) 127.0.0.1 = 9 bytes in size on disk & is the largest/slowest
2.) 0.0.0.0 = 7 bytes & is the next largest/slowest in size on disk
3.) 0 = 1 byte
Using a 0 also eliminates the need to perform the "decimal-to-hexadecimal" conversion process that 127.0.0.1, or even 0.0.0.0 go thru, since 0 decimal = 0 hex... plus, since the filesystem, memory mgt, & caching kernel mode subsystems of the OS itself use 4 kb sweeps/reads/passes to load up, using a SMALLER string via 0 usage (vs. 0.0.0.0 or 127.0.0.1) will tend to "pack" more records into each pass of the read being done, on disk & in memory, per pass/sweep/read as well.
Even "security guru" Oliver Day @ SecurityFocus.com sees using HOSTS as a good thing for added layered security AND MORE SPEED ONLINE -> http://www.securityfocus.com/columnists/491
AND?? So do folks like "SpyBot Search & Destroy" also (since their app populates not only the HOSTS file, but, also files like Opera's Filter.ini, FireFox's block lists, & IE Restricted Zones also, for LAYERED SECURITY (this is the trend & recommended practice by security folks by the by, myself included))
Hey - Even this slashdotter, sootman, uses one & ma
Comment removed based on user account deletion
Bare in mind that netbook hardware is most certainly anything but current. Performance is roughly equivalent to a 5 year old Pentium M. The only difference is that it has been shrunk and power consumption reduced to the point where 5 year old mid class laptop has been reduced significantly in size.
Running Win 7 on a modern mobile (Core 2 Duo) CPU would give a much better comparison, and really show the true benefits it has.
From experience I can tell you that Windows 7 (64-bit version) can be installed on a 10 GB partition. Barely, but it does work.
If you want light, Minix still can't be beat but I don't see anyone using it as a desktop OS. I wonder why.
No problem is insoluble in all conceivable circumstances.
Because most people get whatever their OEM will sell them and stick with it 'til they buy something newer, and those of us who build our own jumped ship to 64-bits *years* ago.
The market of "people not ready to upgrade their 32-bit hardware looking for a new OS" is statistically insignificant.
No problem is insoluble in all conceivable circumstances.
Part of the problem is the hatred of the proprietary, which is a huge deterant for the hardware and software support they actualy need (from video chip makers and adobe) which would allow them to grow up and be an "OS for real people."
Have I got this straight: Adobe is shipping a crappy proprietary flash implementation because the "hatred of the proprietary" deters them from fixing it, not because they think Linux is marginal and not worth spending more time on. So, supposing we really loved proprietary software, Adobe would magically ship better implementations because of... what, karma? It's not as if flash isn't installed on practically every single Linux desktop out there, so they're not going to see a bigger installed base by eliminating this "hatred".
Also, the notion that "real people" would have youtube and browser games as primary concerns is bollocks. "Real people" use Linux and other UNIXen all the time, including for "real work".
In 1993 I had a Compaq Concerto. It was my favorite computer of all time (even more than my Macs that I have now). It was a pen-based machine and also had a keyboard. (Contrary to popular opinion, handwriting recognition actually worked: the catch is that it required the user to adapt and learn how to write so that the system can read your writing. If you were willing to do that, it had a very high rate of recognition.) The machine came with 4Mb or RAM but I put 12Mb in it - and that was considered HUGE at that time. (The battery lasted for four hours, and I had two so I could go for eight hours.) I ran Photoshop with NO PROBLEM on the machine, and many apps at once, including Netscape, etc. - which as you might recall had Java and lots of things bundled into it. I used to program in C++, Java, and Pascal on the thing. I seem to recall that it had a 128Mb disk drive.
So what the heck is the 16Gb of Windows 7 for????? In terms of the value of my computing experience, they are about the same - except that the Concerto would not have been able to handle the large media files of today unless you increased the RAM and disk space - but the OS certainly would not have minded as long as the codecs were installed. And let's not say it is because Windows is now multi-tasking where as Win 3.1 wasn't, because the original Unix was multi-tasking, and it fit in 4k or something like that.
I recall that I once installed Photoshop 3 on a Windows ME machine at a time when the latest version of Photoshop was 7. (Photoshop 7 was designed to run on Macs and Windows 3.1.) It started and was ready to use in under one second!!! And it was lightning fast. Using the current Photoshop of that time required the usual 30 seconds to start up. Yet, Photoshop 3 did everything - it just did not have some of the bells and whistles of later versions that one normally does not use - things that should not be part of the runtime anyway. In any case, any new features were not worth a factor of 20+ in startup time and a similar factor in memory footprint!
So my conclusion is that the current bloatware is somehow designed to be bloated. Something is fishy! Is it the large OS libraries that must be linked in now? The .Net, layered on top of the Win API? (talking about Windows here - similar questions for other OSs.) I suspect that our software could be much leaner, and run on much smaller footprints, and start and run much, much faster, and therefore use much less power - and therefore run for much longer without recharging. Again, I wish someone would decompile the code of some of these programs (and OSs) and see what the extra bloat is actually doing and what the source of it is.
Good point, if there was only some way we could balance things, rather than going to the extremes. Unfortunately, we all know the law, forcing us to adopt either the biggest or smallest OS footprint.
So, if I understand this right: 7 is faster than XP because it offloads things to the GPU XP doesn't do (window compositing)? -S