![]() I also recommend migrating those existing modules that are related to the new modules to ensure complete compatibility.īefore I start with the steps for migration, I have to mention that it is not really “ necessary” to perform an existing Java code migration, and it is only a “ recommendation” to take advantage of the full potential that Kotlin offers. In this situation I recommend to develop the new features or functionalities using Kotlin, and gradually migrate the existing functionality. For these projects it is best to keep what exists in Java, and to program the new using Kotlin. Projects that receive the implementation of some new functionality occasionally. ![]() This type of project is better to leave them as they are, it is not worth investing time and effort in a project that is already in an almost invariable state. Projects that only receive occasional maintenance.Now, maybe you are at the crossroads of “migrate my existing projects” or “leave them as they are”, therefore, according to my experience, I leave a few points to keep in mind: But, if you have already experienced enough to decide that from now on you will use it instead of Java, Congratulations! You have really understood the potential that this language has. If you are starting to use Kotlin, you have most likely created new projects to experiment with this language. ![]() Kotlin is an excellent language and I can say that it has won my preference for the development of Android applications.
0 Comments
Leave a Reply. |