a lot of interesting comments here about swift verses objective C.
Here's my take and experience.
I started in the day with COBOL on punch cards, proceeded to learn the earliest dBase coding for the first PCs and hated it. It turned what were fast machines for the day into painfully slow processes. At the encouragement of a relative who worked for Bell Labs AT&T I taught myself original C and never turned back.
I dabbled with Assembly to improve certain hardware and screen speed issues with the PCs of the day. I was really happy when Microsoft introduced the foundation classes for C++ (it made writing for Windows a whole lot easier) and then came Objective C from the NEXT computer. At first I was a little annoyed that Apple did the Apple thing and deviated from from the C++ standard but after awhile I began to appreciate the small improvements that were made and now wonder why C++ hasn't adopted some of them.
Where's all this going? I like and believe in the structure of Objective C whose origins are 30+ years old from K&R C. Eliminating the brackets, semi-colons and all those types of things to me make the code less disciplined, readable and maybe even less portable.
I also like how Apple has improved the memory allocation and management in their compilers. It beats the old days of chasing down memory leaks and overwriting issues which would crash a program.
Now what do I think of Swift?
If one want's to be a programming professional for Apple products they must know both languages and be a master at one of them. Objective C will not go away in the near future and Swift is still maturing, but learn both and choose one.
Here's my take and experience.
I started in the day with COBOL on punch cards, proceeded to learn the earliest dBase coding for the first PCs and hated it. It turned what were fast machines for the day into painfully slow processes. At the encouragement of a relative who worked for Bell Labs AT&T I taught myself original C and never turned back.
I dabbled with Assembly to improve certain hardware and screen speed issues with the PCs of the day. I was really happy when Microsoft introduced the foundation classes for C++ (it made writing for Windows a whole lot easier) and then came Objective C from the NEXT computer. At first I was a little annoyed that Apple did the Apple thing and deviated from from the C++ standard but after awhile I began to appreciate the small improvements that were made and now wonder why C++ hasn't adopted some of them.
Where's all this going? I like and believe in the structure of Objective C whose origins are 30+ years old from K&R C. Eliminating the brackets, semi-colons and all those types of things to me make the code less disciplined, readable and maybe even less portable.
I also like how Apple has improved the memory allocation and management in their compilers. It beats the old days of chasing down memory leaks and overwriting issues which would crash a program.
Now what do I think of Swift?
If one want's to be a programming professional for Apple products they must know both languages and be a master at one of them. Objective C will not go away in the near future and Swift is still maturing, but learn both and choose one.
