I feel very sorry for you - you just confirmed what I suspected from the
beginning. Now we all know. I have no relations to the original OP, not
geographic, not cultural, and not business other than that we both develop
software for OS X. In this respect he is a foreigner to me, exactly as you
are. I strongly disagree with the views that you expressed here and with the
way you are trying to use this list. I'm convinced that majority of this
list members, and also employees of Apple Computer Inc. and the company
itself do not share your opinions here.
I have nothing more to say right now to you and still remain within the
overall topic of this list.
Bye for now
Dr. Mikael Hakman
Research & Development
Datakonsulten AB
Uppsala, Sweden
On Monday, April 28, 2008 12:25 PM, Laurence Harris wrote:
On Apr 27, 2008, at 11:21 AM, Mikael Hakman wrote:
On Thursday, April 24, 2008 9:44 AM, Laurence Harris wrote:
On Apr 23, 2008, at 6:39 AM, Mikael Hakman wrote:
While we are on the nomenclature issue, we should as well explain
that Macintosh, in this context, is name of personal computers
produced currently by Apple. It is a hardware product. Today, you can
run various operating systems on this hardware platform, including OS
X
As long as we're being precise about nomenclature, it's Mac OS X, not
OS X.
You are correct; the name of this operating system is "Mac OS X". You
omitted "X" is your previous message. I omitted "Mac" in mine. I did it
intentionally, in order to clearly show the difference between today's
Mac hardware and various operating systems possible to run on this
hardware.
, Windows XP and Vista, Linux and more. Also by using virtualization
software you can simultaneously run more than one OS on this
hardware.
Therefore, one often overlooked, easy and not requiring large effort
way to port an application (or a system of applications) from Windows
to Mac, is to boot Windows on Mac and then run unchanged Windows
applications.
This is like saying you're porting Windows to Dell.
No, in my world it is like saying you're porting an APPLICATION to
Inspiron (one of Dell's hardware lines)
That's probably true.
This set is commonly called "Boot Camp". You could argue whether this
action of Apple should be called porting or supporting.
I think of porting as a process that involves changing the ported product
to run in the new environment. Since Windows isn't modified to run on a
Mac under Boot Camp, I think of it as supporting.
You could also argue whether the thing that virtualization software does
should be called porting or supporting.
I don't really think of it as either. ;-)
When anyone talks about porting a Windows application to run on the
Mac (we'd never say "run on Mac" in English), they are referring to a
Mac OS, which nowadays means Mac OS X. So what you describe isn't
porting a Windows app to the Mac, it's just running a Windows
application on a Mac running Windows.
I don't know what the correct idiosyncrasy in your culture is but the
objective of my somewhat ironic message was to lift the roof on this
thread a little bit higher. After your suggestion that people would be
more receptive if the OP wrote Mac, not MAC, and after the other
sarcasms expressed by you versus the OP, I felt that the roof has come
down to such a lows that I had difficult to breathe. An immediate acute
reaction was inevitable.
Maybe from you, but I was just being honest and others have said the same
thing in the past. You may not like it, but for better or worse, if you
are going to come here and ask people who have spent years learning
Carbon -- often in a time-consuming, tedious, and frustrating process
because of an almost complete lack of documentation -- to share their
knowledge to help you, you should have invested some time first learning
about the Mac and have at least a basic understanding of what involved
developing for it. Certainly you should be able to *write* Mac correctly.
After all, it's written "Mac" everywhere it appears on hardware, in the
OS, and on Apple's web site. When you come here asking for help and can't
even write "Mac" correctly, it doesn't look good.
Actually, a big part of the problem is how people like the OP come across
here. There's every indication that the OP is in a foreign country like
India where programming companies bid for work in competition with
programmers and companies here, but for a variety of reasons they can
seriously underbid their competition here. They get the project and
assign someone who clearly has no Mac experience to work on it. Then he
comes here to ask people who have the knowledge and experience he lacks
how to do what he needs to do. But these are the very people the client
wasn't willing to hire because they charge more than the programmer with
no Mac programming experience. Not everyone here appreciates that, and a
little effort on the part of the programmer, such as at least taking the
time to notice how "Mac" is spelled can go a long way toward showing
respect for the people whose help they're requesting.
The OP asked 3 straight-forward and simple questions.
He asked questions that strongly suggest he hasn't does his homework
about how Mac software works and how to port Windows software to the Mac.
In particular, even after multiple people answered his first question by
telling him that simply replacing APIs is not the right approach, he
asked another one of those questions.
Each of these questions could have likewise straight-forward and simple
answer. In fact I believe they have, in particular the first two. If you
don't know what these APIs do or you don't know Carbon's answer then the
right thing to do is to keep quiet.
You are not the list administrator. I've been on this list at least six
years now, and I'm too old for you to raise me, so whatever you think
you're going to accomplish here, it's not going to work.
If you want to discuss alternative implementations or designs then the
right way is to get some experience what these APIs actually do and then
discuss this functionality in the light of Carbon. Being mastering and
sarcastic versus OP is wrong way. He needs help and information, not
noise and repulsion.
He needs to take some time to understand how Carbon works and is
fundamentally different than Win32. Whether you like me saying it or not,
people are generally more willing to help someone who has invested time
and energy trying to understand things before coming here. If you come
here asking people to tell you how to do things before you've learned the
fundamentals, it really doesn't go over so well.
Furthermore, and regarding also some of your response to me, there is a
strong but unspoken rule on every international forum, of which this
list is one. People natively speaking the language chosen as forum's
communication language, may not, and should not use this coincidental
fact to master others or take an advantage of this fact in a discussion.
And I have not done that.
On the contrary, everyone is doing his best to read WHAT the other
people say, not HOW they say it.
I do, or at least I try. But when I've learned other languages, I've
always appreciated being corrected so I could do better and so others
wouldn't have to compensate for my mistakes, so I treat people the way
I'd like to be treated. But FWIW, I really don't know what you're trying
to say when you say "mastering" someone. In English, to master something
is to learn it well. To be mastering something means you're in the
process of learning it well.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
