Get the ECT News Network Editor's Pick Newsletter » View Sample | Subscribe
Welcome Guest | Sign In
Digital River - Talk to the Experts
E-Commerce Times TechNewsWorld CRM Buyer LinuxInsider

MacNewsWorld Talkback

ECT News Community   »   MacNewsWorld Talkback   »   Re: Apple Move Not So Juicy

Re: Apple Move Not So Juicy
Posted by: Howard Solomon 2005-07-25 07:57:07
See Full Story

Weeks after Apple Computer's decision to start switching to Intel processors, the industry is still digesting the news. However, not all of the company's resellers think the news is juicy, with at least one disappointed at the holes in the announcement. For example, missing are details about which Intel processors will be in the new Macs, to be released 12 months from now. That will affect the ease of porting Apple applications to the new system.

Re: Apple Move Not So Juicy
Posted by: tkuechle 2005-07-25 15:49:35 In reply to: Howard Solomon
In the article I don't see any mention of what other PC makers will be using in terms of CPU's. I would speculate that Apple will use whatever CPU is appropriate for their needs and I strongly believe that other PC makers will also do this. Why is the article written in a semi-alarmist style, I don't know and besides all of the major changes will not even begin for about a year from last month, but it really will not mean anything to most users.

Re: Apple Move Not So Juicy
Posted by: xyzzy 2005-07-25 12:10:50 In reply to: Howard Solomon
As a longtime Mac developer and as someone who is very familiar with the announcement and the transition kit, I don't understand the point of the article. The article raises questions about which processors would be used. Wouldn't it be the same processor that appears in the transition kit? If you buy the transition kit, you get a Mac with an intel processor in it to use for a period of time (it eventually has to be returned to Apple).
So, if your program works on the machine supplied in the transition kit, I would imagine that it would also work on the Intel based Macintoshes when Apple ships them next year.
Second, maybe I am missing something, but I seriously doubt that Apple's move to Intel will make it any easier to port a Windows app to the Mac. That is, an application written using the Win32 APIs or the Windows MFC APIs would still need to be rewritten to use the Cocoa or Carbon APIs. Applications written for .net will not run on Mac any easier because of intel processors. Modern application are very rarely written in assembly language and, even if they were, they would still be making system API calls which would be different on the Macintosh. As a developer who writes for both operating systems, I can't think of a single way in which moving to Intel would help anyone port an app to the Mac.
Windows emulator? Yes, that would probably operate more efficiently, but native apps? No.
Am I missing something here? Is there some big class of apps written in pure x86 assembly without Windows system calls?

Re: Apple Move Not So Juicy
Posted by: reboylin 2005-07-25 09:14:07 In reply to: Howard Solomon
This transition will be easier than in the past with a program available that runs legacy code for OS X in emulation on the same desktop with a speed around 75% of native applications. Many developers had already gotten their programs running within 3 days while attending the developer's conference. Some, who had adopted Apple's universal binary development suite as reccommended could simply recompile for the next PCs.
Jump to:
If my employer requires me to return to the company's office full-time to perform my job, I will...
Agree, because I like my job regardless of where I perform my duties.
Comply, because I can't afford to lose my current job.
Go with the flow, but start looking for different employment.
Resign immediately, so I can dedicate all of my time to find a job that better suits my needs.
Try to negotiate a hybrid work from home / work in office arrangement with my employer.