Re: Carbon -> Cocoa
"older OS versions", porting to 10.6 or later vs. 10.10 or later: I at first intended all the drivers I write for my clients to work on Snow Leopard 10.6, but after actually attempting to do so I settled upon supporting El Capitan 10.11, sometimes just Sierra 12.6. There are some occasional but quite serious problems with new APIs appearing during a minor release so you can't just set your Deployment Target to a major release's first drop. To get drivers to build - and I expect Cocoa code as well - one must take _great_ care to check Apple's doc for most if not all of your API calls to determine when they first appeared. For one particular client's USB function driver we actually had three kernel extensions. I at first planned to package this in just one kext bundle but because of time pressure shipped them as three separate ones. Two of the drivers had Deployment Targets of 10.12, the third 10.11. I had some manner of good reason for doing it this way, but I've just been up all night nosediving deeply into Wikipedia and all manner of Epic Talk Page Flame Wars so just now I'm too thrashed to actually remember what it was. Mike Crawford Portland Custom Software Development http://soggywizards.com m...@soggywizards.com One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light ___ 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
Re: Carbon -> Cocoa
It might be the new Carbon once: - there is ABI stability in Swift. This could be not before late 2019. - the new APIs are only available in Swift. Is Swift NIO a hint this is coming sooner than expected? I don't know. I don't use networking frameworks. Regarding the complexity of porting from C++ Carbon to Cocoa, there's also the important question of what your minimum OS target is. Maybe one of the reasons why you kept a Carbon version alive so long is that the application needs to keep working on older OS versions. Porting to OS X 10.10 or later is not the same thing as porting to 10.6 or later for instance. On Thu, Aug 16, 2018 at 3:48 PM, Sean McBride wrote: > On Thu, 16 Aug 2018 11:54:59 +, Casey McDermott said: > >>I am curious, are there other developers on this list working on conversions >>from C++ Carbon to Cocoa? > > By now, Cocoa may be the new Carbon. > > If you haven't switched to Cocoa after all these years, and if your app is > large, I'd wait to see what happens with Marzipan. > > Sean > > > ___ > > 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/dev.iceberg%40gmail.com > > This email sent to dev.iceb...@gmail.com -- Packaging Resources - http://s.sudre.free.fr/Packaging.html ___ 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
Re: Carbon -> Cocoa
A while back I offered to port a PowerPlant Carbon app to Cocoa for sometime who posted it on one of the contract programming sites - ucode or some such. We agreed on his total price but he absolutely _refused_ to agree on pre-agreed milestones. I always put such milestones in the contract, as well as mailing back and forth with my clients as to what each milestone should actually be, my pay for reaching each milestone as well as what ACCEPTANCE TESTS my code must pass so as to trigger a payment. The reason this joker gave for being so obstinate was that he once paid one of my Friendly Competitors for some networking code WITHOUT EVEN LOOKING AT IT, that Friendly Competitor bailed, then his next Friendly Competitor coudn't make sense of the first one's code. I remain _dumbstruck_ that anyone at all would either propose, agree to or actually pay for a milestone without both sides agreeing to the acceptance tests which are SPECIFIED IN THE CONTRACT. Don't even get me started. Just Don't. -- Mike Crawford mdcrawf...@gmail.com The Global Computer Employer Index: http://soggy.jobs/computer (It's actually starting to get global now.) On Fri, Aug 17, 2018 at 5:53 PM Jerome Krinock wrote: > > > > > On 2018 Aug 17, at 10:43, Andreas Falkenhahn wrote: > > > > On 17.08.2018 at 19:37 Casey McDermott wrote: > > > >> Of course, the C++ business logic doesn't need any changes. The concern > >> is, > >> how long will it last? > > > > Well, I'd guess that C++ is pretty future-proof. > > Swift is itself written in C++ :) > > > ___ > > 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/mdcrawford%40gmail.com > > This email sent to mdcrawf...@gmail.com ___ 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
