[kkirsche]

I’m not convinced by the argument as it sounds like it’s tone implies that it’s written to people who aren’t aware of who their audience is.

Sure, not all of these tools are right for all audiences, but that doesn’t mean that they aren’t good suggestions for wide swathes of the ecosystem.

I think it’s important instead to think about your largest user groups and provide workflow ideas for those groups. For example, with Python we may have (this is a simplified list):

* Web Development * Data Science * Embedded * Compilation / Transpilation (e.g., PyO3)

Of these groups, I’d expect the tools mentioned to be reasonable for two or three of the groups, but less so in groups like data science where there is a higher concentration of non-development first specialties.

There are always outliers, but I think choosing your target audience is important. On a team, I wouldn’t necessarily want to teach a person a random workflow if the team all uses one of these types of tools.