> The worst result - which I've seen far too many times - is that new-tech only 50-80% replaces old-tech - and now you have to maintain both. i’ve seen this to

> The worst result - which I've seen far too many times - is that new-tech only 50-80% replaces old-tech - and now you have to maintain both. i’ve seen this too, (in apps) where there are 3 different “reactive” libraries in use that all do the same thing smh.. my feeling is, if you are going to change out the technology, then to avoid said problem of maintaining both, is the change needs to happen very very quickly to avoid having to maintain the old one while getting side-tracked to implementing new features and the transition gets sidelined... its very difficult to pull off