4 ms·
This is just a visual and fairly shallow similarity. I think the context switch is huge and the same as Objective C. Anyway the future isn’t Swift, it’s JavaSc
by ajeet_dhaliwal 9y ago
This is just a visual and fairly shallow similarity. I think the context switch is huge and the same as Objective C.
Anyway the future isn’t Swift, it’s JavaScript for everyone :-)
- kalleboo 9y agoAltho TBH most of the objections I've heard against ObjC from non-ObjC developers usually are just as shallow and revolve around how weird or ugly the bracket syntax for messages is.
- valuearb 9y agomy objections to obj C are code quality, pointers and crash rates.
- abritinthebay 9y agoVisual affects reading which affects comprehension. Don’t dismiss visual similarities so out of hand.
- ajeet_dhaliwal 9y agoIt matters yes, I’ve never been completely comfortable with Python and Lua because of their style but in the example above how is the Swift better than the Objective-C? Sure the params syntax is cleaner here but then you have the return type (with the ugly arrow) at the end instead of the start of the line which is unusual compared to many other c style syntax languages and you also lose the -/+ instance/class method syntax i always liked in Objective-C. JavaScript of course doesn’t have to supply a return type at all, I just don’t see how any of this helps someone coming from JS/Python/Ruby combined with the deeper understand required around nullables and types.
- wootness 9y agoFor everyone? Yeah, no.