Re:The Rise of Microsoft Visual Studio Code
by dagw on Friday December 07, 2018 @03:10AM
(#18625924)
There's nearly always another language to use to get the job done
Sure, but in most cases programmers spend most of their time only in one 'part' of the system and only really have to know the language that part of written. In general it doesn't matter if the back end server is written in Lisp, Java or APL, as long as it talks to my part of the system in the way it's supposed to.
Re:The Rise of Microsoft Visual Studio Code
by danans on Friday December 07, 2018 @10:12AM
(#18628267)
> in most cases programmers spend most of their time only in one 'part' of the system
Perhaps that's a reflection of the structure of the organizations they work in.
Anyways, the other cause of multilingualism is switching jobs, projects, or problem spaces. All three of those often involve a language switch.
This surprises me as I've never worked on a nontrivial system that's also a monolingual system.
There's nearly always another language to use to get the job done, whether for configuration, scripting/automation, or because backends and UIs are written in different languages, especially for internet-based software.