I actually don’t use C++ with Objective-C - in fact, I flat out hate it from the half year being forced to use it in a CS course. Actually I even created a rough Foundation clone and migrated almost all programming paradigms from Objective-C to C++. Compare this:
CCArray *array = CCArray::alloc().init(object).autorelease(); and this: NSArray *array = [[[NSArray alloc] initWithObject:object] autorelease]; Rang any bells my friend? However the reason preventing me from jumping onto the Swift bandwagon so far is two points: 1) language stability and 2) Linux support. Swift did not stabilise to a useable state so far (regarding the release version, not the prerelease) for me, and I cannot support my high count of Linux servers using Swift code. Objective-C, however, is stable (at least as long as I am using LLVM compiler, regardless of version, as long as the code compiles and all required features, like ARC, is supported) and GNUstep provided a good Foundation clone on Linux (since all my Linux hosts are servers, AppKit have no use to me, but GNUstep team also did a good job on that department too) to the point that most of my server side code can be written and debugged under latest version of OS X and Xcode, and it will work after a recompile linking against GNUstep libraries under Linux. > On Jun 14, 2015, at 14:44, Paul Scott <psc...@skycoast.us> wrote: > > >> On Jun 13, 2015, at 3:59 PM, Quincey Morris >> <quinceymor...@rivergatesoftware.com> wrote: >> >> I don’t want to take issue with the opinions being expressed in this thread, >> but I was struck by the argument you used in coming to your opinion: >> >> On Jun 13, 2015, at 15:27 , Paul Scott <psc...@skycoast.us >> <mailto:psc...@skycoast.us>> wrote: >>> >>> in practice there is little to justify the existence of Swift […] >>> >>> When C++ and Java appeared on the scene, I initially struggled to >>> understand the value they offered, but I soldiered on knowing that there >>> may be value beyond my understanding. That perseverance was well deserved, >>> and over the decades I’ve come to appreciate the tremendous practical value >>> both languages provide […] >>> >>> […] Swift insinuates itself into the developer community with typical >>> grandiose marketing hype. But what practical value does it really offer? >> >> You persisted with C++ and Java in spite of your skepticism, and eventually >> found value. >> > > There was never skepticism. I was careful not to use that word or a > derivative. I could see potential in both Java and C++ from the beginning but > it took a great deal of time before I discovered the true value they offered, > in part — but just so — because the languages themselves needed to evolve > over the decades. I did not say my perseverance paid off. I said it was well > deserved. > > By contrast, having looked at the overall features of Swift — as I said, > perusing the documentation, watching the relevant WWDC videos, weighing the > pundit’s arguments (mostly positive) — and its interoperability with Cocoa, I > still find nothing compelling enough to justify switching from an > Objective-C/C++ mix that has served me well. > > The topic of this thread is “Language options: Objective-C, Swift, C or C++,” > so my intent was to show that despite all the hype, Swift doesn’t provide me > with enough practical value to switch. I also wanted to express my fervent > hope that Objective-C/C++ will continue to be supported and mix freely with > each other. Simply one developer’s opinion, FWIW. > > Of course, the suitability of a language also depends on the environment in > which it’s employed and the particular problem requiring a solution. > Certainly, Swift fills a role for some. But, it’s also a bit of a square peg > being jammed into a round hole for others. I’ll pass, for now. > > If you’re not using C++ freely with Objective-C, then Swift might be the tool > for you. > > Paul > > > > _______________________________________________ > > 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/max%40maxchan.info > > This email sent to m...@maxchan.info
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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
