[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: It's not that easy

Subject: Re: It's not that easy
From: Cliff Pruitt <email@hidden>
Date: Wed, 14 Sep 2005 11:27:03 -0400
Delivered-to: email@hidden
Delivered-to: email@hidden

OK Just so I knew I wasn't crazy I did a quick search & found this:

http://developer.apple.com/documentation/DeveloperTools/Reference/ Assembler/i386Instructions/chapter_7_section_1.html

Among other things on this page: "This chapter contains information specific to the Intel i386 processor architecture, which includes the i386, i486, and Pentium processors."

and "Note: Don’t confuse the i386 architecture with the i386 processor. Darwin makes use of instructions specific to the i486 and Pentium processors, and will not run on an i386 processor."

Now, for the record, I can barely get an NSSplitView to do what I want let alone know enough to understand anything related to this assembly stuff, but at least I'm not so off my rocker that I'm just making up architecture names.

:-)

As far as chip names though, I'm going to miss the simplicity of G3, G4, G5... You've got one processor to worry about and thats it. With Intel you've got a 'Pentum', and you've got a 'Xeon', and then back a while you had a 'Pentuim III Xeon'... well which was it? A Pentium or a Xeon? (Before I get a bunch of replies telling me which or neither of them it was... I really just don't care. [grin]) I'm a Mac guy. Call me spoiled but I guess I do get frustrated when people don't go well out of their way to do all my thinking for me. :-) I'm not used to things being complicated and even as I'm getting into Cocoa I still don't want them to be complicated. Thats not the Mac way is it? And though I have no doubt it'll make sense with exposure to it, its still enough to make me roll my eyes at Intel in general. Hopefully Apple has them developing one processor and I don't have to pay attention to the whole alphabet soup of it all. Probably too much to hope for...


- Cliff


On Sep 14, 2005, at 8:40 AM, Ricky Hussmann wrote:

Just for fun:
http://www.intel.com/museum/online/hist_micro/hof/
http://www.pcmech.com/show/processors/35/
=o)
On 9/14/05, Cliff Pruitt <email@hidden> wrote:
I don't quite know all the terminology ins & outs.  I was under the
impression the intel architecture was called "i386" but I might just
be out of my mind.  I wasn't quite referring to a 386 mhz processor!
(grin)
I'm just waiting to see the first Mac with a four inch "Intel Inside"
sticker plastered across the front...
(When they start bundling AOL I'm jumping ship...)
:-)
Cliff
On Sep 14, 2005, at 6:27 AM, Finlay Dobbie wrote:
On 14/09/05, Cliff Pruitt <email@hidden> wrote:
On Sep 13, 2005, at 4:11 PM, email@hidden
wrote:
Mactel Computers
...
"Intel Based Mac" or "386 Mac" would be just fine if a distinction is needed, but remember that eventually All Macs will be intel based

I would be worried if we start seeing Macs with 386 processors ;-) Currently, we don't know what the branding of any release hardware will be, and "Macintosh with Intel processor" (as used by the UBPG) is a bit verbose.
 -- Finlay
_______________________________________________ Do not post admin requests to the list. They will be ignored. Student-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/student-dev/ricky.hussmann% 40gmail.com
This email sent to email@hidden
--
Ricky Hussmann
Associate Engineering Scientist
West Virginia Virtual Environments Lab
Morgantown, WV

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Student-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/student-dev/email@hidden

This email sent to email@hidden

References:
	>Re: It's not that easy (From: Cliff Pruitt <email@hidden>)
	>Re: It's not that easy (From: Finlay Dobbie <email@hidden>)
	>Re: It's not that easy (From: Cliff Pruitt <email@hidden>)
	>Re: It's not that easy (From: Ricky Hussmann <email@hidden>)

Prev by Date: Re: Ruby and Cocoa
Next by Date: Framework Linking Problem
Previous by thread: Re: It's not that easy
Next by thread: Re: It's not that easy
Index(es):
- Date
- Thread

Home