4 ms·
Doing a rewrite of, say, an APL system without programmers with a really deep understanding of APL on the team will most likely end in failure and misery. So y
by dagw 15y ago
Doing a rewrite of, say, an APL system without programmers with a really deep understanding of APL on the team will most likely end in failure and misery. So you're still faced with the problem of finding and hiring people who know APL. Also letting some RoR hacker, who heard about APL for the first time 3 days ago, loose on your super critical production code, probably isn't that great an idea either
- gaius 15y agoA former employer spent literally 9-figures on repeated attempts to port a legacy app from VAX BASIC to C++ on Unix. God only knows how much they would need to do APL...
- jharsman 15y agoProvided you still have source code and development tools available, the problem in cases like this usually isn't the language. Even APL is pretty easy to pick up if you have a book or someone to teach you. The bigger issue is that the application you need to fix is mission critical, undocumented and contains massive amounts of spaghetti code. There usually aren't any tests, source control might not be used and it's far from certain there are automated builds or deploy scripts. In some cases you might not even have source or the tools to use it, and then you have much bigger problems. But the language usually isn't the main problem.