News for hackers. Stuff that matters.
Re:How many languages/frameworks is too much for back end? by PaulHoule on Monday January 01, 2018 @01:05PM (#16047138)
The problems with too many programming languages are: (1) it is harder for somebody to jump in at an arbitrary place, which is particularly bad for maintenance, where it is not unusual that a "simple" bug fix requires changes to parts written in multiple languages and (2) code frequently winds up being duplicated, both of the "business rules" variety and of the system and technology specific kind.

As an example of the latter, consider a service written in Go that may need stubs written for it in several other languages.

I have seen the cost of polyglot development to be high in teams up to 20 or so developers. When you have 120 developers it less reasonable to expect that one person can jump in anywhere, so the reasons for multiple languages multiplying will eventually overwhelm the coherence benefit of using a minimal number of languages.

Occasionally too there really is a "right tool for the job" or rather right tools for different jobs. Most of the commercial NLP devs I know who have a codebase they work on use both Python and Java since there are many great libs in both languages.

There are no comments on this comment yet.