• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Need for Swift
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need for Swift


  • Subject: Re: Need for Swift
  • From: Laurent Daudelin via Cocoa-dev <email@hidden>
  • Date: Mon, 14 Oct 2019 23:44:36 -0400

I’ve been wondering the same thing. I thought that maybe because I was biased
toward Obj-C. But if it wasn’t for the editor, damn, I don’t know how many
times I would have to go back to unwrap one of those optionals. Are people
supposed to know instinctively when you unwrap with “?” and when you do with
“!”? I’m not there yet, even though I’ve been doing almost a year of Swift so
far...

-Laurent.
--
Laurent Daudelin
                email@hidden <mailto:email@hidden>
Skype: LaurentDaudelin
Logiciels Némésys Software
http://www.nemesys-soft.com/ <http://www.nemesys-soft.com/>

> On Oct 14, 2019, at 22:43, Alex Zavatone via Cocoa-dev
> <email@hidden> wrote:
>
>
>
>> On Oct 14, 2019, at 1:25 PM, Carl Hoefs via Cocoa-dev
>> <email@hidden> wrote:
>>
>> The group that likes Obj-C sees Swift as being "arbitrarily syntactical"
>> with the syntax of the language getting in the way of programming. (There is
>> a third group that likes both languages, but it is very small.)
>
> I am in this group.  The syntax of Swift just feels so arbitrary and to look
> deeper to solve more problems… if it weren’t for those compiler messages, it
> would be a mess.  I, for one shuddered when I saw “if let x = y” being
> something that people are expected to use and that damn, “you must unwrap
> this optional”, simply ends up making things that were simple in Objective-C,
> completely cumbersome in Swift.
>
> And this “everything is an extension”?  That is hell.  I love classes
> adopting protocols where the class definition of the variable must be weak,
> because you can’t do it in the protocol and oh, whar?  This proticol needs to
> be class backed?
>
> So much clunk to do what we could already do with ease.
>
> But then again, my team is using VIPER and in none of the code reviews did
> the lead call in to question that every var was strong.  And they wonder why
> we had 3410 memory leaks.
>
> I’m not yet a fan.
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Need for Swift
      • From: Charles Srstka via Cocoa-dev <email@hidden>
    • Re: Need for Swift
      • From: Quincey Morris via Cocoa-dev <email@hidden>
References: 
 >Need for Swift (From: Kirk Kerekes via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Richard Charles via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Laurent Daudelin via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Pier Bover via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Charles Srstka via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Carl Hoefs via Cocoa-dev <email@hidden>)
 >Re: Need for Swift (From: Alex Zavatone via Cocoa-dev <email@hidden>)

  • Prev by Date: Re: Need for Swift
  • Next by Date: Re: Need for Swift
  • Previous by thread: Re: Need for Swift
  • Next by thread: Re: Need for Swift
  • Index(es):
    • Date
    • Thread