> That will depend on what the GP has done with SQL. I am sure they built their UI with SQL - as opposed for example simply doing some queries, or some joined

> That will depend on what the GP has done with SQL. I am sure they built their UI with SQL - as opposed for example simply doing some queries, or some joined procedures at best. > Also, JQuery implies in Javascript. With uttermost likelyhood, they did not only dynamic changes of some html-documents there, but also their backend and crypthography. Enough with the snark... ("Language" is such a fuzzy term anyways. You could go as far as to label any interaction with a computer as one - there will always be a protocol according to which the interaction happens.) > There should be plenty of people capable of taking the codebase, but it's not a trivial single language case. The upside is that good developers will be overrepresented when compared to the population that knows one of Python or Javascript. I still stand by my point. As far as the cost of polyglotism is concerned, that is a one-general-purpose-language-codebase and the rest being DSLs (apparently R too). There are other codebases where there are really 2+ languages. I.e. some functional lang on top, some performance critical code hand-written in C, some logical programming language to do some constraint programming. Each of those 3 takes quite a lot experience.