The post discusses the different aspects to consider when comparing programming languages, including soil (properties of running code), surface (features and syntax), and atmosphere (community and ecosystem). It also explores why discussions about programming languages often focus on atmosphere and the challenges of quantifying its impact. The author argues for a more open-minded approach to tech choices and suggests that training and mentorship can help developers quickly become proficient in new languages.
Table of contents
When you compare languages, what are you actually comparing?Discussions get less concrete as you go upwardsThe current thinking is "atmosphere at all costs!"Is it hard to learn a language?……most commodity devs don't know much about Boring Stacks everyone chooses. Also, they don't generalize across companies!Why are we at "atmosphere at all costs"?Sort: