At the point when Apple reported Swift,
I heard a couple of individuals say "Yahoo! Presently I can be an iOS engineer
without learning Objective-C!" I have three messages for these
individuals:
On the off chance that you need to be an
iOS
designer, you will at present need to know Objective-C.
Objective-C
is less demanding to learn than Swift.
When you know Objective-C, it will be
anything but difficult to learn Swift.
Before I continue, let me introduce this
with an admission of affection for Swift. The linguistic structure is
exquisite. The Swift compiler will get such a large number of blunders for us;
I'm sure that when everybody is coding in Swift the unwavering quality of
applications will enhance significantly. The enum build is perfect. Quick is a
noteworthy advance forward for the whole iOS and Mac
OS X biological community. In any case…
In the event that you need to be an iOS
designer, you will in any case need to know Objective-C
You can't do everything in Swift. For
instance, in the event that you need to utilize a library of C++ code in your
application, you should converse with the C++ objects from Objective-C. Quick
can call C capacities, however I trust that on the off chance that you are
working with a great deal of C capacities and sorts, you will need to code in Objective-C.
The people group talks in Objective-C.
There are a huge number of helpful Objective-C scraps on StackOverflow and iOS dev writes
all around. Objective-C is the dialect we have utilized throughout the previous
six years to portray to each other how the Cocoa Touch libraries function. On
the off chance that you can't read Objective-C, you won't have the capacity to
comprehend this trove of learning.
The structures are composed Objective-C.
When you have a bug, it regularly doesn't raise its monstrous head until the
point that execution is somewhere down in Apple's code. In the event that you
need to comprehend what the debugger is letting you know, you should comprehend
Objective-C.
Objective-C is steady and very much
tried. Quick looks incredible, however the dialect is advancing and the
compiler is youthful. In the event that I were making a critical wager on
building up an application this year, I would in any case utilize Objective-C.
Objective-C is less demanding to learn
than Swift
C is a truly basic little dialect, and
Objective-C is a truly basic little augmentation to C. Quick has many tenets
that Objective-C does not. (I, as an educator, am as of now endeavoring to make
sense of how I will clarify the standards around discretionary factors and the
best possible utilization of ? what's more, ! to flag the software engineer's
expectation around optionality.) These additional principles imply that the
compiler can be significantly more pompous about implementing great coding
rehearses, yet it likewise implies that the dialect will take more time to
learn.
Objective-C expects software engineers
to be express. The Swift dialect gives the compiler a chance to accomplish more
work for the software engineer. This is extraordinary—less writing for the
software engineer, right?— however it implies that when you take a gander at a
line of code, it won't mean much without a profound comprehension of the
setting in which that line lives. Unequivocal dialects are less demanding for
amateurs to get it.
Quick has a bundle of builds that
Objective-C doesn't have. For instance, generics improve sort checking in
Swift, however it makes that dialect significantly more intricate.
When you know Objective-C, it will be
anything but difficult to learn Swift
To make Swift interoperable with
Objective-C, Apple needed to make Swift a great deal like Objective-C. The
troublesome thoughts that drive Objective-C like items, solid and powerless
references, and legacy are precisely the same in Swift—they are quite recently
communicated utilizing an alternate sentence structure.
Truly, it doesn't make a difference
which you learn first; in the long run you will know the two dialects.
No comments:
Post a Comment