programming languages - Why do you or do you not implement using polyglot solutions? -


polyglot, or multiple language, solutions allow apply languages problems best suited for. yet, @ least in experience, software shops tend want apply "super" language aspects of problem trying solve. sticking language come "hell or high water" if language available solves problem , naturally. why or not implement using polyglot solutions?

i advocate more 1 language in solution space (actually, more 2 since sql part of many projects). if client likes language explicit typing , large pool of talent, advocate use of scripting languages administrative, testing, data scrubbing, etc.

the advantages of many-language boil down "right tool job."

there legitimate disadvantages, though:

  • harder have collective code ownership (not versed in languages)
  • integration problems (diminished in managed platforms)
  • increased runtime overhead infrastructure libraries (this significant)
  • increased tooling costs (ides, analysis tools, etc.)
  • cognitive "bumps" when switching 1 another. double-edged sword: well-versed, different paradigms complementary , when problem arises in 1 there "but in x solve z!" , problems solved rapidly. however, don't quite grok paradigms, there can real slow-down when trying comprehend "what this?"

i think should said if you're going go many languages, in opinion should go languages different approaches. don't think gain in terms of problem-solving having, say, both c# , vb on project. think in addition mainstream language, want have scripting language (high productivity smaller , one-off tasks) , language different cognitive style (haskell, prolog, lisp, etc.).


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -