In the Apple paradigm, I click on the Lion upgrade in the App Store (it knows I already purchased it). It installs, and we're done – no reboot. Just a video tutorial on new features.
In the Microsoft paradigm, I'm digging up DVD cases to manually type product codes that require me to needlessy recreate my upgrade path and make decisions about things like 32bit vs. 64bit. It's still installing Vista I type this, and the progress bar has been stuck at 75% for about an hour. The user experience: a scaled-up 640x480 installer that has been on the "Completing installation..." step for two hours.
It baffles me why anyone would affirmatively seek out this experience. As for the Intel "ultrabooks" – more vaporware from the 1990's-era PC industry. The "rest of us" have moved onward and upward.
EDIT: Windows installer just spit the DVD out and froze. Can't move the mouse. Time to start over! (I can almost hear them: Have you tried turning it on and off again?)
EDIT 2: If anyone is following this, attempt #2 failed the same way. This is hour 10 of trying to install Vista on a clean MacBook Pro 2010.
EDIT 3: Gave up and installed a VM through Fusion. Ironically, this is easier than a native Windows install.
Have you tried installing Lion on a non-Apple notebook? You seem to be making a very unfair comparison.
FYI – I've had Vista/Win7 installed on this machine before. It's a question of how horrible the process is. Typing in product codes, inserting DVDs, activation codes, warnings about anti-virus, etc.
You don't have to type product codes -- you can install without one and copy/paste from a text file works fine once you're all set up. You don't have to insert DVDs, Windows installs fine from a USB stick (except on Apple notebooks, so there). Installing Microsoft Security Essentials will shut up any AV warnings.
Besides, you don't even need to install Vista to get an upgrade copy of Windows 7 working. A Google search would have told you that.
EDIT: Not sure why I'm downvoted for asking this. Can anyone advise as to what hardware issues would make a 2010 Macbook Pro more difficult to install Windows on?
Anyway, I use Windows for exactly one thing: accessing (horrible) web apps that require IE. My original point was that the installation process is a mess from the perspective of a licensed user – Apple hardware or not.
Win 7 won't accept my product code because it is an upgrade code. I googled it.
Also, my benchmark is the Lion upgrade. That's how it's supposed to work.
Installing Lion on a non Apple Mac is illegal and that's why it is so hard to do. Windows is not and should run smoothly like on every other machine.
Having had all this trouble, I don't believe that for a second. Turning off AHCI and not supporting USB boot in 2011 is inexcusable.
Installing Lion on a non Apple Mac is illegal
Depends on the jurisdiction. In many non-retarded ones it isn't.
Windows is not and should run smoothly like on every other machine.
It should, yes, but it doesn't.
These don't look like vaporware.
http://www.engadget.com/2011/09/01/lenovo-announces-u300s-ul... http://www.engadget.com/2011/09/02/acer-aspire-ultrabook-s3-... http://www.engadget.com/2011/09/01/toshibas-portege-z830-is-...
Here's a bold plan that will kill two birds with one stone: Buy Canonical, throw the bulk of your $300 Million at their development, poach/cajole/trade for every UX guru not employed by Apple, and create a killer Linux desktop OS to go along with that ultrabook. It will scream, it will run a battery all night long and beg for more, it will have no "hells" (.dll, dependency, driver, symbol, whatever "hell" is inherent in Windows and Linux), it will run a plethora of online apps and services, and it will host a complement of installed applications that take care of 95% of a mainstream consumers needs.
No need to install flash, it's already there. Need to play an .mkv file? No problem when VLC is installed by default. Netflix on demand? At your fingertip. Amazon mp3 store embedded in banshee? Sure, why not? Writing a term paper or presentation? LibreOffice to the rescue.
Reinstalling Windows should not take more than 15 minutes, it should require no user-interaction, and it should leave the data partition alone. The data partition is where users images/photos/videos/music go. Intel should work with MS to ensure that executables do not run from this partition. If my mom downloads a virus, she shouldn't have to call me to fix it. Hardware DEP hasn't done much to stop viruses. Intel needs to come up with hardware features to remedy root-kits without my assistance.
Intel thinks of itself as one of the hardware makers with competitors. It makes CPUs, like AMD or Samsung. It makes boards like MSI or ASUS. This is red ocean. It needs to make its own blue ocean and of all the companies in the PC industry, it is actually capable of doing that. Instead of offering $300m to others, it should put $3B into creating the single Ultraboard that any PC seller can build a case around and sell tens of millions of these. Dell can't do it. Sony can't do it. Intel can. Just like Apple did.
I agree that the user experience needs to improve across the Windows 8 platform for this to really matter, but that is mainly in Microsoft's court.
For me, I like having both a Mac and PC on hand. An Ultrabook would be nice if only for the size.
It might be an issue of scale but not portability. Much less software exists for Mac than does for Windows.
Using a vm/jit isn't the only way to handle architecture changes. In addition it doesn't remove the need to handle kernel changes/etc... that the vm itself runs on. Nor does it mean that the vm and all of its underlying assumptions are valid on a new instruction set. It took java a fair amount of time to run fast on multiple architectures, I doubt .NET will fare any better.
When Windows actually manages to (again, it ran on alphas/mips/ppc and something else back in the 4.0 days) run on more than one platform I might partially buy into .NET being "portable" across windows releases and architectures. But I suspect a fair amount of things will have to change or move to new apis. Similar to Microsofts go it alone 64bit model in Windows, another architecture in the fray will force things into spaces they didn't originally expect.
Basically, I don't trust anything coming out of Microsoft until they deliver the goods. Apple has shown they can handle multiple platforms transparently, and without the need of a vm/jit. Which can help out things like battery life with caches/etc...
http://en.wikipedia.org/wiki/Mach-O http://en.wikipedia.org/wiki/Fat_binary#NeXT.27s.2FApple.27s... http://en.wikipedia.org/wiki/Rosetta_(software)
Also, .NET is "portable" not just across Windows releases, but through the work of Mono large portions of it also work on Linux, and on other architectures via Linux as well -- so presumably, anywhere Mono or Microsoft's official .NET are compiled, .NET will run so long as no weird x86- or binary-specific things (like P/Invoke) are done. There are other problems with Mono, however, but those are for another discussion.
The only use Rosetta served was running cross architecture binaries.
Mono also doesn't run the full .NET stack, e.g. think the Netflix drm components, so I can't quite consider it cross platform. Cross platform windows wise sure, but that isn't saying much.
The technology demonstration included Windows client support across a range of scenarios, such as hardware-accelerated graphics and media playback, hardware-accelerated Web browsing with the latest Microsoft Internet Explorer, USB device support, printing and other features customers have come to expect from their computing experience. Microsoft Office running natively on ARM also was shown as a demonstration of the full depth and breadth of Windows platform capabilities on ARM architecture.
I dont think there is reason to doubt Microsoft on API compatibility which i s what this ultimately boils down to. Windows recently ran on IA64 BTW. .NET helps but Win32 in itself is proven enough to need little more than just a recompile for porting.
But in fact their 64bit abi on x86_64 was in fact derived from their 32bit calling conventions.
http://stackoverflow.com/questions/4429398/why-does-windows6...
Correct me if I'm wrong, but there is an exact case of where 32bit windows on x86 directly influenced 64bit. This is what I'm talking about when I talk about other 64bit platforms may not behave the way Microsoft expects. And this directly influences c/c++ register allocation.
Though I will state, what Microsoft did for its fastcall on 32bit windows and 64bit is rather ingenious in that the same call can work on both platforms.
Most of the time, the differences are hidden by abstractions in the Win32 C API. The calling conventions do a pretty good job of this (especially the 64-bit ones). Still, there is a nontrivial amount of software that does need to use a few (or many) assembly instructions or interact with the CPU in low-level ways. Windows is a relatively friendly OS for applications that rely on non-standard behavior.
You can't "just port" an antivirus package. Certainly many malware samples won't run on ARM either, but many will (like .vbs). It will take time to sort all that out. In the meantime, many companies simply won't deploy Windows without AV.
For example, MS Office and IE are still used primarily in 32-bit mode on 64-bit systems.
Even if everything goes smoothly with the codebase, just setting up another build environment for something like ARM means installing a new compiler version and toolset. Many (or most) dev shops are stuck on 6-10 year old compilers.
You also multiply the QA regression cycle costs by some incremental factor.
There are lots of applications small and large, that to this day, don't even ship a 64-bit build.
Yes, there are some applications that have been ported. Even if you were to come up with a not-short list of them I would submit everything else in the world that has not.
Traditionally, MS has been very good at maintaining compatibility through different versions. Maybe they'd make an architecture change easily, but they haven't had to do so yet.
I even know someone who's seen a non-x86/64 Windows system!
Sorry. I concede that there is a major application or three that runs on Itanium. For now. Microsoft is dropping the platform.
As for ARM all I'm saying is we'll wait and see.
The big different is not technology, it's culture. Apple will happily make all your old software obsolete as long as it doesn't seriously interfere with them selling new hardware. Microsoft has the much harder job: they need businesses to buy OS licenses (that is what they sell) and those businesses have a lot of old crappy expensive software that must continue to run to make the sale.
Wake me up when 50% of the shrinkwrapped Windows-logo compliant and hardware software sitting on store shelves runs on it at native speed.
Apple doesn't sell spec sheets. They sell end-to-end integrated systems. A 7 second boot time doesn't mean as much when it gets me to a relentless stream of "the webpage you're at wants to open a webpage you trust - are you sure?" and other user-unfriendly operations. Total experience sells. The iPad is beating the pants of tablets with twice the specs - but half the user experience.
Intel is aiming at where Apple is now. When Intel arrives there, Apple will have moved on. Don't build what I want, build what I'm going to want a year after I buy it a year from now.
And for that $300M plan, Apple has $30,000M cash to counter it. Get in the right order of magnitude first before picking a fight.