I've never seen a single person that used Office web apps except for playing around with them.
I do see the trend towards laptop though. But many people that bought a netbook soon got buyers remorse - because most of them jsut aren't powerful enough.
I've used Vista since the end of 2006 on my media center, on my desktop at home and on my work laptop.
I've never experienced any crashes on those machines. I did see crashes on customer machines, though. Analyzing the crashdumps with windbg usually revealed a faulty driver, antivirus package or broken hardware to be the root cause.
I like how people can judge an OS just because whoever sold you that piece of hardware fucked up the base image.
I've never felt a need to do a performance comparison between XP and Vista, because the latter always offered enough performance to do all the tasks i need to do.
Sure, there might've been a small speed improvement in certain cases, but the same can be said for any older OS. It doesn't matter.
Well, if you really insist on doing an inplace upgrade, you can do that. I would heavily suggest you do create an image of the drive first, and test this on another hard drive.
Do an inplace upgrade to Windows Vista SP1. No CD key needed. Do another inplace upgrade to Windows 7.
This will take hours, depending on the speed of the machine. There's a good chance that most of the stuff will be broken afterwards.
I've never had any issues with migrating my laptops or computer. I've always upgraded from one Windows 7 build to another using a clean install. In about 3-4 hours, i was done getting everything back into order to work. Most of that time was spent waiting on programs to complete, with no interaction needed.
There's a multitude of possible migration paths to take, to go from Windows XP to Windows 7 - in fact there is only one migration path that's exclusive to Windows Vista - the inplace upgrade.
The inplace upgrade is a horribly bad idea, and you should never try or consider it.
So, for any reasonable person, the migration paths available from XP to 7 are exactly the same as from Vista to 7. A new, clean install, followed by a migration of application settings.
If you're a home user, use Windows Easy Transfer to save all your settings to an external drive, reinstall, then recover your settings from the external drive. Reinstall all apps.
If you're a business user, there's a wealth of options available to you - check out the documentation for MDT2010, which can provide you with all the tools you need to roll out Windows 7 in your company. USMT and Windows Easy Transfer are the same under the hood - so user settings can be migrated.
I'm not comparing it to XP because i haven't used XP as my desktop OS since the end of 2006 - 3 years ago.
Most of the customer machines that are still on XP and i use from time to time are a lot slower than my laptop running Windows 7 - they're also running on slower hardware, so it's not a fair comparison.
Microsoft's "Engineering 7" blog has several telemetrics examples from Windows 7 vs. Vista.
As a Microsoft Partner, we've been using Vista exclusively on good hardware (2.5+ Ghz Intel Dualcores, 4GB RAM, 32bit Vista Enterprise).
We've completed our Migration to Windows 7 x64 two weeks ago. That's 10 desktops and 20 laptops. Everyone that has moved to Vista to 7 is glad that their computer is now faster.
Personally, i've witnessed that it's quicker to respond, though the tasks take roughly the same time in the end.
XP x64 shares service packs with Windows Server 2003, and is built upon the same code base.
The reason why XP x64 has gained the "it sucks" reputation is mostly due to missing consumer drivers for XP x64. Almost all decent server hardware supports WS03 x64, but there is a lot of consumer out there that was never supported on XP x64.
Since Microsoft has made x64 support mandatory for Vista upwards, this has changed greatly. Vista SP1 and WS08 are built upon the same code page, just like WS08R2 and Windows 7 are. This makes drivers support easy - and now with Windows 7, many manufacturers start shipping a x64 OS by default (which makes sense - 4GB of RAM isn't "much" anymore).
Firefox offers an option for addons installed on the system level, and not on the user level, like the addons you manually install are.
This makes sense for example in a company, where you deploy Firefox to desktops - you'll want for addons to be installed on a system, and not a per-user base.
Lenovo's quality of the "real" ThinkPads (T-series, X-series, W-series) is still pretty good.
The R-series have always been not-as-good. What Lenovo did was to introduce the SL-series, which are crap.
I've been using a T60, until i needed more power and switched to the W500 in last december. It's a great machine. I'm using it with Windows 7 x64, with WS08R2 on a VHD to run VMs through Hyper-V.
They do care, however, about SLAs. And that's all you need. I wouldn't care much if a 3rd party doesn't care about my business the same way I do. I care that he cares about SLAs between they and us.
Yes - and now look how extremely low the SLA is that comes with Google Apps. Specifically, they have no guarantee against data loss. You have to do your own backups - which kinda negates the whole "managed service" aspect.
This isn't really an issue if you know what you're doing - but many people simply think that services like these won't ever fail.
People should always be able to take a joke. That includes everyone women, men, jews, arabas, mexican, blacks, fat people etc.
I still don't get the permanent bitching about being politically correct with everything. There are formal and informal places - and most FOSS mailing lists are one of the latter.
And this informality is one of the reasons why doing this is attractive - because you can go out and state your opinion. I wouldn't tell a coworker "your idea sucks and you should shut the fuck up", because it would be bad for the workplace. In a more informal setting, you can do that.
If you have local infrastructure, and you run into an issue, there's at least something you can do. For example, if your internet connection fails, it might be possible to hack something together to get email working again, for example using an UMTS Router.
Or if your Exchange server fails, you'll be able to get SOME backup restored, even if you can only take weekly backups because management said tapes are expensive.
If Google has a total system crash and loses 98% of it's data, but would be able to restore the remaining 2% at very high expenses, do you think they'd do it? Probably not.
Disclaimer: I use Google Apps Premier for my private domain.
Slashdot Mirror
We've been using the RC on about 20 ThinkPads. Not a single one of them had issues or functionality that didn't work. One of them was an X200 tablet.
None of them had issues with installing (we upgraded from Vista). By now, we've upgraded all of these to the RTM version. No issues either.
Maybe you shouldn't buy HP.
I've never seen a single person that used Office web apps except for playing around with them.
I do see the trend towards laptop though. But many people that bought a netbook soon got buyers remorse - because most of them jsut aren't powerful enough.
So if i drive a car after drinking gin i'm less likely to crash?
Yeah, but XP was basically the same to Windows 2000. And we all know how that turned out.
I've used Vista since the end of 2006 on my media center, on my desktop at home and on my work laptop.
I've never experienced any crashes on those machines. I did see crashes on customer machines, though. Analyzing the crashdumps with windbg usually revealed a faulty driver, antivirus package or broken hardware to be the root cause.
I like how people can judge an OS just because whoever sold you that piece of hardware fucked up the base image.
No, i'm talking from my personal experience.
I've never felt a need to do a performance comparison between XP and Vista, because the latter always offered enough performance to do all the tasks i need to do.
Sure, there might've been a small speed improvement in certain cases, but the same can be said for any older OS. It doesn't matter.
Time moves forward, not backward.
Well, if you really insist on doing an inplace upgrade, you can do that. I would heavily suggest you do create an image of the drive first, and test this on another hard drive.
Do an inplace upgrade to Windows Vista SP1. No CD key needed. Do another inplace upgrade to Windows 7.
This will take hours, depending on the speed of the machine. There's a good chance that most of the stuff will be broken afterwards.
I've never had any issues with migrating my laptops or computer. I've always upgraded from one Windows 7 build to another using a clean install. In about 3-4 hours, i was done getting everything back into order to work. Most of that time was spent waiting on programs to complete, with no interaction needed.
There's a multitude of possible migration paths to take, to go from Windows XP to Windows 7 - in fact there is only one migration path that's exclusive to Windows Vista - the inplace upgrade.
The inplace upgrade is a horribly bad idea, and you should never try or consider it.
So, for any reasonable person, the migration paths available from XP to 7 are exactly the same as from Vista to 7. A new, clean install, followed by a migration of application settings.
If you're a home user, use Windows Easy Transfer to save all your settings to an external drive, reinstall, then recover your settings from the external drive. Reinstall all apps.
If you're a business user, there's a wealth of options available to you - check out the documentation for MDT2010, which can provide you with all the tools you need to roll out Windows 7 in your company. USMT and Windows Easy Transfer are the same under the hood - so user settings can be migrated.
A good place to start is the Windows 7 springboard:
http://technet.microsoft.com/en-us/windows/default.aspx
I'm not comparing it to XP because i haven't used XP as my desktop OS since the end of 2006 - 3 years ago.
Most of the customer machines that are still on XP and i use from time to time are a lot slower than my laptop running Windows 7 - they're also running on slower hardware, so it's not a fair comparison.
Virtualbox supports multiple VCPUs.
Windows can do CPU microcode updates:
http://support.microsoft.com/kb/936357
Only the 64bit versions do. Granted, all UEFI enabled machine (except some Macs) are 64bit capable, but it's still important.
Microsoft's "Engineering 7" blog has several telemetrics examples from Windows 7 vs. Vista.
As a Microsoft Partner, we've been using Vista exclusively on good hardware (2.5+ Ghz Intel Dualcores, 4GB RAM, 32bit Vista Enterprise).
We've completed our Migration to Windows 7 x64 two weeks ago. That's 10 desktops and 20 laptops. Everyone that has moved to Vista to 7 is glad that their computer is now faster.
Personally, i've witnessed that it's quicker to respond, though the tasks take roughly the same time in the end.
What, you can't dial using your mind?
XP x64 shares service packs with Windows Server 2003, and is built upon the same code base.
The reason why XP x64 has gained the "it sucks" reputation is mostly due to missing consumer drivers for XP x64. Almost all decent server hardware supports WS03 x64, but there is a lot of consumer out there that was never supported on XP x64.
Since Microsoft has made x64 support mandatory for Vista upwards, this has changed greatly. Vista SP1 and WS08 are built upon the same code page, just like WS08R2 and Windows 7 are. This makes drivers support easy - and now with Windows 7, many manufacturers start shipping a x64 OS by default (which makes sense - 4GB of RAM isn't "much" anymore).
We were able to order Windows 7 OEM, Retail and Upgrade licenses on the 15th. We received the first ones on the 16th.
This is in no way unusual...
I guess you can see it that way, but in the end the .NET framework isn't an optional part in Vista or 7 (it was in XP - you may opt not to install it).
Firefox offers an option for addons installed on the system level, and not on the user level, like the addons you manually install are.
This makes sense for example in a company, where you deploy Firefox to desktops - you'll want for addons to be installed on a system, and not a per-user base.
The .NET utility just made use of that.
Lenovo's quality of the "real" ThinkPads (T-series, X-series, W-series) is still pretty good.
The R-series have always been not-as-good. What Lenovo did was to introduce the SL-series, which are crap.
I've been using a T60, until i needed more power and switched to the W500 in last december. It's a great machine. I'm using it with Windows 7 x64, with WS08R2 on a VHD to run VMs through Hyper-V.
Not in every country. And then there's Tor.
Yes - and now look how extremely low the SLA is that comes with Google Apps. Specifically, they have no guarantee against data loss. You have to do your own backups - which kinda negates the whole "managed service" aspect.
This isn't really an issue if you know what you're doing - but many people simply think that services like these won't ever fail.
I've heard plenty of jokes about Swiss and fat people. I don't have an issue with either.
People should always be able to take a joke. That includes everyone women, men, jews, arabas, mexican, blacks, fat people etc.
I still don't get the permanent bitching about being politically correct with everything. There are formal and informal places - and most FOSS mailing lists are one of the latter.
And this informality is one of the reasons why doing this is attractive - because you can go out and state your opinion. I wouldn't tell a coworker "your idea sucks and you should shut the fuck up", because it would be bad for the workplace. In a more informal setting, you can do that.
Being 100% nice and 100% honest isn't possible.
Yep, but consider this:
Google doesn't care about your university.
You did. Or at least should've ;)
If you have local infrastructure, and you run into an issue, there's at least something you can do. For example, if your internet connection fails, it might be possible to hack something together to get email working again, for example using an UMTS Router.
Or if your Exchange server fails, you'll be able to get SOME backup restored, even if you can only take weekly backups because management said tapes are expensive.
If Google has a total system crash and loses 98% of it's data, but would be able to restore the remaining 2% at very high expenses, do you think they'd do it? Probably not.
Disclaimer: I use Google Apps Premier for my private domain.
They have to, all Xeon based machines require it.
Just like all other Xeon based workstations.