andrewhw00 wrote:
Nothing I have said it meant to be a "pot shot".
Let's see what the dictionary says:
pot·shot| ˈpätˌSHät |
noun
a shot aimed unexpectedly or at random at someone or something with no chance of self-defense: a sniper took a potshot at him.
• a criticism, especially a random or unfounded one: the show takes wickedly funny potshots at movies.
You insulted Apple developers behind their back by calling their work "sloppy".
Your criticisms are completely unfounded.
Ergo - a "pot shot".
Stating that an error has actually occurred upon observing the vendor provided software, when run in a vendor approved way, produces an error message isn't a pot shot.
It is a warning, not an error. The tool still works doesn't it? Ergo, no error.
My observation that I am disappointed to learn that this likely is occurring because of a longstanding unmanaged misbehaviour at a lower level is not meant to be a "pot shot" either -- just an honest observation of a user of this system.
"I'm also just a user, standing in front of a developer, asking them to be less sloppy"
I don't see how the number of devices shipped, nor any measure of market capitalization as you mentioned earlier, has anything to do with this situation.
Not once did I say anything about "market capitalization".
I did suggest that having written operating systems for over a billion devices, in dozens of different hardware configurations, and to have done so successfully, strongly suggests that Apple engineers know what they are doing and that your criticisms of sloppy work are absolutely false and unfounded.
I am now perplexed by your statement that "Developers normally do not see this particular message for various reasons that are clearly not worth explaining." This directly contradicts what you said earlier. Is this, or is this not, a common error message in the developer console?
OK. I'll try again. I never, not even once, said this was a common error message in the developer console. You simply misunderstood.
I said this has been a common error message for at least a decade. I didn't bother to mention that this has been a common error message in the Terminal for a decade because at that time, I had no idea how my statements were going to be so wildly twisted and misunderstood.
I also said that Apple likes to emit very verbose information to log systems of all kinds. I mentioned the developer console as one particular place where Apple's log messages can get out of hand. I also mentioned the Console app (completely different than the developer console, by the way) as another place where Apple's log messages can have the unintended consequence of driving people who are already mentally unstable into insanity.
To clarify, this specific message "Class <name> is implemented in both /path/to/dylib1 and /path/to/dylib2. One of the two will be used. Which one is undefined." is a normal, harmless, warning message that has been printed on the Terminal and in log files by Apple software for many years.
As I have noted, error messages of this form are certainly NOT commonly produced on standard error.
Message of this form are commonly produced on standard error.
If all you are offering is that there are lots of messages on the developer console, and that you therefore expect users of the system to simply ignore any error messages that they see, then this is, I am afraid, not useful information.
I must have neglected to mention this, but you are referring to a warning message, not an error message. If it had been an error message, then it should have been associated with some type of system or app failure. You were running opendiff, correct? Did opendiff fail in some way?
I previously suggested that users who are unaccustomed to logging messages should avoid the Console app. I think it would be better if they avoided Terminal as well, since Terminal will often emit various console messages. (Note, by "console" here, I am not referring to the Xcode debugger console, nor to Apple's Console.app, but rather, the normal behaviour of text-based tools being executed from a command-line environment.)
