> it could be a legacy and baggage if the authors resist to change.

Every few years there is a new batch of programming languages that come out and they all gain a small passionate community that tries to convince the internet how much better that language is.

They inevitably use the argument that code not written in the new language is 'legacy' and 'resistant to change'.

Neither of those assertions are accurate or enlightening unless you can provide a proposed replacement and prove the superiority of the new code.

Simply telling other programmers to rewrite there code in xyz language with such arguments is primarily a case of armchair development.

If you really think it could be done better then do it and prove it.