Language Selection

English French German Italian Portuguese Spanish

Apple to Switch Macs to Intel Chips

Filed under
Mac

In a risky move that could further shrink its minuscule slice of the PC market, Apple Computer Inc. announced plans Monday to switch its Macintosh computers to the same Intel Corp. chips used in systems that run Microsoft Windows.

Apple, which for years suggested its users "Think Different," will join all other PC makers in using microprocessors built on the x86 architecture. The technology took root when IBM launched its first PC in 1981 and eventually turned Apple into a niche player.

"Our goal is to provide our customers with the best personal computers in the world, and looking ahead Intel has the strongest processor roadmap by far," said Steve Jobs, Apple's CEO. "It's been ten years since our transition to the PowerPC, and we think Intel's technology will help us create the best personal computers for the next ten years."

Jobs said Apple will begin offering Macs with Intel processors by June 2006 and will switch its entire product line by the end of 2007.

Copyright 2005 The Associated Press.

UPDATE: args! /. beat me!!! Anyway, if you haven't seen their submitted post, they link to the Keynote er..notes. Big Grin Here!

Linux

I wonder how this is going to affect Linux usage. Most poeple moved to Linux to get away from crappy MS products. Mac OS is safe and secure and looks great.

OS X won't be available

After Jobs' presentation, Apple Senior Vice President Phil Schiller addressed the issue of running Windows on Macs, saying there are no plans to sell or support Windows on an Intel-based Mac. "That doesn't preclude someone from running it on a Mac. They probably will," he said. "We won't do anything to preclude that."

However, Schiller said the company does not plan to let people run Mac OS X on other computer makers' hardware. "We will not allow running Mac OS X on anything other than an Apple Mac," he said.

Source

So, I don't see it doing much of anything to Linux.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Systemd 216 Piles On More Features, Aims For New User-Space VT

Lennart Poettering announced the systemd 216 release on Tuesday and among its changes is a more complete systemd-resolved that has nearly complete caching DNS and LLMNR stub resolver, a new systemd terminal library, and a number of new commands. The systemd 216 release also has improvements to various systemd sub-commands, an nss-mymachines NSS module was added, a new networkctl client tool, KDBUS updates against Linux 3.17's memfd, networkd improvements, a new systemd-terminal library for implementing full TTY stream parsing and rendering, a new systemd-journal-upload utility, an LZ4 compressor for journald, a new systemd-escape tool, a new systemd-firstboot component, and much more. Read more

Desktop Obsessions, Steam Sacrifices, and LibreOffice Review

We've been reading a lot about the desktop lately and we're not stopping tonight. We have three stories tonight on the desktop. In other news, the kernel repositories beef-up security and Alienware says Steam Machine users will "sacrifice content for the sake of Linux." The new Linux version of Opera is making progress and CNet has a review of LibreOffice 4.3. This and more in tonight's Linux news. Read more

Black Hat 2014: Open Source Could Solve Medical Device Security

On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse? Read more

Does government finally grok open source?

Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way. That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors. Read more