> 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
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
