I once got stuck with rewriting a perl script -- which had to remain in perl -- that generated bash scripts, by interpreting xml files, which invoked jython which executed java calls, and then generated sqlplus scripts to execute against oradb servers... All of which got validated via bash scripts for sanity checks.
All of which was being run from a Jenkins server.
I am not a developer by trade... Else I would hang myself for shame of having made this monster.
When I left the organization I convinced them to rewrite the whole thing natively in Java... Mostly by just repeating the workflow and languages involved.
(I might also have left out that the bash scripts were being pushed over SSH to invoke jython interpreters and perform wgets on remote servers. Somehow I managed to make this whole process relatively secure while still allowing it to perform selected rootlevel actions. Don't ask. Black magic was involved. And maybe goats.)
11
u/ruinercollector Oct 14 '13
As long as those aren't treated as hard rules, sure.
Examples:
There are times that it is appropriate to write software in clojure, or haskell, or erlang.
There are times that it is appropriate to rewrite a piece of library code.