> Of course, I knew that cargo-culting... You're cargo-culting the phrase "cargo-culting" here, i.e. using the term blindly without understanding it. Using a

> Of course, I knew that cargo-culting... You're cargo-culting the phrase "cargo-culting" here, i.e. using the term blindly without understanding it. Using a programming language and related frameworks repeatedly, based on prior first-hand success, is not anywhere near the definition of cargo-culting. > ...every time I start a new project, I question what language I should use for it... Sounds like a waste of time unless the projects are significantly different from each other in terms of environment or requirements. The most productive and efficient choice is very frequently the language/frameworks your team know best. If that's not weighing extremely heavily in your decision-making process, you're doing it wrong.