4 ms·
> After that, convert it to a static language I don't think you can have a hard and fast rule like this. It will depend on the situation. In many instances, a
by saila 5y ago
> After that, convert it to a static language
I don't think you can have a hard and fast rule like this. It will depend on the situation. In many instances, a "prototype" built in Python or similar is perfectly fine.
In addition, one can make a horrendous mess in statically typed languages as well. One of the absolute worst projects I ever worked on was written in a popular statically typed language. This is of course an anecdote and not to say statically typed languages are worse, but they're not automatically better either.
Just a note too that I'm a big fan of, e.g., Rust & TypeScript, and I often use type hints in Python, so I'm not anti-static typing.
- dimitrios1 5y agoWay easier to refactor a that statically typed mess. There is a floor for how bad you can write static typed code. There is no floor to how bad of JavaScript or Python or Ruby you can write. The madness can descend to the inner most circles of coding hell. Only Perl exceeds it.