Whats the frequency of the letter t in:
Q: Migrate from an architecture to another I have an existing Java architecture that uses a basic proprietary framework.
I want to start developing new functionalities in a framework, ex Play.
In that way I will not lose existing functionalities, I will replace them slowly and I will probably end up seamlessly with a rewritten application.
Is this wise to do? Or there are other better ways to face this kind of transition from one framework to another?

A: So, you have an application using an old, rusty framework A, and you want to move towards framework B.
This is a type of refactoring that can happen due to a lot of reasons, most of which can be reduced to we dont want framework A as a dependecy anymore. Reasons can be varied, such as A is not maintained anymore, B has nicer features and so on. 
This definetly happens. However, the transition is hard and painful. The safest way to transition is to create separate branches, where you transition a piece of the application. Never mix transitioning with new development, since, if something goes wrong, is hard to trace. 
But, in the end, think if it is worth it. Yes, B might be better, but is it good enough to be worth the cost of refactoring/revalidating the whole project?

user
The passage contains 102 "t"s.
assistant