On Feb 22, 2014, at 10:09 PM, dangerwillrobinsondan...@gmail.com wrote: > There is no Cocoa to this. This is OT.
That is absolutely not true, it is *entirely* a question of Cocoa API, but…. > Thread should end. …I’ll actually request the thread end, because it has unfortunately been swallowed by emotions, rather than holding to the simple question of nuts and bolts. This was nothing more than a question of can the machine (OS X) be made to do function X. I went further to describe the actual use-case, as that is a common first question received when seeking a solution, for the purposes of illustrating the need and the challenge — not for instigating a discussion of how unreasonable my clients are, how the use-case is suspicious and must be in some way nefarious, etc. Debating the merits of the use-case was not the point — the potential function of the machine was the point. Not all security measures are useless just because there’s another potential breach elsewhere, or because an underground cabal operating in a secret lair within a volcano can crack it using a satellite orbiting the Earth. I am not tasked with solving all of those issues, even if they are legitimate issues. I am tasked with solving exactly the functions I asked about — which are direct no-ops for large customer contracts. I’ve got a fair pulse on the mailing list response, which in general is “you’re dumb for asking” (points for consistency — it was much the same when I posted about this a year ago). I’m not that cynical, I see the merits in the need (and for that matter, Apple’s own engineers did too when we sat down and discussed it in person). Furthermore, solving the problem brings keeps this app on OS X, and allows a large number of educational and professional users around the world to use Macs for their needs, rather than have these institutions / organizations have to tell their testers “you must run Windows”. Secure, remote testing isn’t going away — it is a huge market only in its infancy — and if anyone wonders how OS market share swings, this is an example — ignoring market needs. So in the future, if you are getting a Master’s degree, and your college tells you that a Windows PC is a pre-requisite, well, you can dig up this thread in the Cocoa-dev archives and have an example of why requirements like that come to be. If it is up to me, that won’t be the case — I’m the eternal optimist, and hope to solve the problem in a manner acceptable to content providers, and keep people testing on Macs. I still can’t post a DTS issue, and I’ve had no response yet from Mac Dev Program support, but hopefully I’ll eventually get through and get some help there. Thanks for the folks who responded offline. Your feedback was extremely helpful. Cheers, Brad _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
