|
|
|
|
|
by izacus
3656 days ago
|
|
> In all cases, it is hard to argument the move to a new language in an existing codebase when there is no official push in that direction. I don't understand the logic behind this sentence? Why do you need Google to push you somewhere instead of you youself choosing a more productive option? Kotlin is designed to be easy to integrate into existing Java codebase and our introduction to a largeish Android codebase has been a great success. |
|
However, right now I am a senior engineer working on a 8 years old android app alongside 15 other Android devs.
The switch to another language is not even something that the current lead or the CTO are willing to consider.
In their defense, we would have to train the whole team, this would be a major task and build times are already a big issue so anything degrading them is hard to push for.
A push from Google would help a lot, it would remove a lot of objections like "this is hipster shit" or "I am not going to learn the language of the month" (coming from people who have not learned any language in years) and force them to take it seriously.
Even the iOS team barely use Swift though, so I don't see it in a near future. I guess I just have to search for another company.
> our introduction to a largeish Android codebase has been a great success. Do you mind sharing some details ?