| Right, I have never been in a situation that a re-write was considered in another language that it was not due to some other reason. Most of the time it is first, we need to change some major functionality, we have an architectural issue, or something along those lines that will require a major re-write in the first place. So the idea of, maybe we should use a different language comes up. The idea of re-writing something in another language and it is identical functionality just for the sake of using another language just isn't a normal exercise unless you have a CTO pushing for something unnecessarily. Maybe, maybe I could buy saying we don't want to manage Java servers anymore or something along those lines. But even then, why break something that works. This seems like such a bad idea, is going to introduce so many bugs, require a ton of testing, for a minimal at best gain? And then yeah, who is going to maintain it given that no one actually wrote the code in the first place. Goodby historical knowledge and productivity. Hope you don't find a critical bug as soon as you release it that needs to be fixed asap. Don't do this, a seriously bad idea. That assumes that it is somehow a 1:1 functionality which by now we should be well aware that an LLM is going to make mistakes. |