As a beginner in iOS development, I am not particularly familiar with UIKit and CocoaTouch of iOS. Although there is code in the document, it is still a little far away from the requirements for use in actual projects, and the third party of swift There are not that many frameworks, and when you actually develop applications, you may encounter problems of one kind or another, which will make you anxious. So for the current Swift, I think we should focus on the use of the Swift language itself, and it does not have to be used in the production environment. Now is not the time to completely replace OC. I believe that swift will replace the current position of OC in iOS development in the near future. Coupled with Apple's current promotion, this process should not take too long, so there is still a need to learn.
Another: Looking at the current momentum, Swift is likely to become the language of the year this year.
1. Treat it as a brand new language and get to know it without the baggage of Cocoa and OC.
2. It is predicted that OC will still be the mainstream in a few years. If Apple does not take any measures, this situation may continue for a long time.
3. With a solid foundation in OC, you can focus on Swift learning. The language promoted by Apple itself will definitely be a key support in the future. This is more important than anything else.
It’s still the Cocoa framework, but the syntax is more convenient to write. It doesn’t make much sense to switch to old projects. The risk of using new projects is slightly higher. You can play with personal projects.
PS:
In fact, I think this matter depends on the attitude of the masters and whether the relevant libraries can follow up.
I haven’t paid much attention to these, but Python3 has been released for so long, and the mainstream is still stuck on Python2
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
As a beginner in iOS development, I am not particularly familiar with UIKit and CocoaTouch of iOS. Although there is code in the document, it is still a little far away from the requirements for use in actual projects, and the third party of swift There are not that many frameworks, and when you actually develop applications, you may encounter problems of one kind or another, which will make you anxious. So for the current Swift, I think we should focus on the use of the Swift language itself, and it does not have to be used in the production environment. Now is not the time to completely replace OC. I believe that swift will replace the current position of OC in iOS development in the near future. Coupled with Apple's current promotion, this process should not take too long, so there is still a need to learn.
Another: Looking at the current momentum, Swift is likely to become the language of the year this year.
I am not a senior, let me share my understanding.
1. Treat it as a brand new language and get to know it without the baggage of Cocoa and OC.
2. It is predicted that OC will still be the mainstream in a few years. If Apple does not take any measures, this situation may continue for a long time.
3. With a solid foundation in OC, you can focus on Swift learning. The language promoted by Apple itself will definitely be a key support in the future. This is more important than anything else.
It’s still the Cocoa framework, but the syntax is more convenient to write. It doesn’t make much sense to switch to old projects. The risk of using new projects is slightly higher. You can play with personal projects.
PS:
In fact, I think this matter depends on the attitude of the masters and whether the relevant libraries can follow up.
I haven’t paid much attention to these, but Python3 has been released for so long, and the mainstream is still stuck on Python2
As an iOS developer, I suggest that the two can learn simultaneously.