I DONT agree that Windows 7 Should be 64-bit only, for one reason my pc is JUST BARELY too old, Dell XPS Gen 3 (Gen 5 IS 64 compatible), is NOT 64 compatible but with windows 7 still packs a performance punch.
Agreed - but I still think it should be the default if it's being installed on a system that is 64 bit capable.
It had better one hell of an improvement. XP's defrag is COMPLETELY WORTHLESS. I doubt I will EVER use a M$ defrag again. Your better off with O&O.
Frankly, I don't bother with defragging in Vista/7 except to set the schedule.
Instead, I buy as much memory as possible and minimize disk use. I still have it defrag, but I reduce the neeed to worry about it.
on a side note hopefully they have not fixed the upgrade loop hole in 7 that past upgrades have had....ie. the ability to preform a clean install with an upgrade disk. I would prefer to do a clean install vs an upgrade just as an opportunity to clean the system up a bit.
In all honesty, I think they should just merge the two into one product that allows both upgrading and clean installs. Forget having two products at two prices.
. . . and you are right, in all honesty it's almost always far better to do a clean install than an upgrade. Usually by the time a new OS comes out it's time to clean up the computer anyways.
My problem with this unfortunately-durable dev fad is not sonmuch with the efforts to make 'intuitive' designs, although I believe strongly that an 'intuitive' interface is an eye-of-the-beholder thing and not some 'truth' that you can find with rigorous research.
Yes and no. While it is true that individual tastes can vary, it is possible to collect statistics on the habits of most users, and more often than not there are very clear trends.
In addition, there are some common principles you can find in UI design. My engineering book has a chapter in UI design with the folowing three "golden rules":
- Place the user in control.
- Reduce the user's memory load.
- Make the interface consistent.
I seriously doubt those principles can be argued - although sometimes the details can.
There's an article by Joel Spolsky about UI design that I recommend reading.
I like this quote of his:
Asking the user to make a decision isn't in itself
a bad thing. Freedom of choice can be wonderful. People love
to order espresso-based beverages at Starbucks because they get to make so many choices
. Grande-half-caf-skim-mocha-Valencia-with-whip. Extra hot!
The problem comes when you ask them to make a choice that they don't care about.
This pretty much sums up what I see in a lot of places where the UI seems wrong to regular people, but power users claim it's right. The power users love having an extreme amount of customization, but regular users just want to focus on the primary task. Sometimes, the customization gets in the way of getting stuff done.
It all really boils down to this: Know your audience.
The one biggest, fatal mistake of poor UIs is that the developers swear that their way is right (and can even explain it), but it conflicts with how it's really used by the users.