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                                                                
                laur...@nemesys-soft.com <mailto:laur...@nemesys-soft.com>
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 
> <cocoa-dev@lists.apple.com> wrote:
> 
> 
> 
>> On Oct 14, 2019, at 1:25 PM, Carl Hoefs via Cocoa-dev 
>> <cocoa-dev@lists.apple.com> 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 (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/laurent%40nemesys-soft.com
> 
> This email sent to laur...@nemesys-soft.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

Reply via email to