> I can see why they want to give users the option

I completely dislike the practice of giving options for no reason other than to give options. Don't make me learn different ways of doing the same thing to succeed in an ecosystem. Don't make me learn differences and similarities. If one way works properly and doesn't have obvious downsides, stick with having one way. If it has obvious downsides, stick with having a different one way. Subjective format taste isn't a real downside. Pick one format and stick with it.

The line from the zen of Python about how "there should be one-- and preferably only one --obvious way to do it" is something that people all too often forget the value of.

> If one way works properly and doesn't have obvious downsides, stick with having one way. If it has obvious downsides, stick with having a different one way.

What if you're in the real world with tradeoffs? So you have both obvious downsides and obvious upsides mixed in each option, and what's more important, those depend on the user, not you, so you can't pick one best option?

That's the reason you give options, and you don't need to learn different ways, learn one you like better or just flip a coin

The irony of quoting the Zen of Python in a discussion about a package manager. I can think of at least three Python package managers off the top of my head.

> The line from the zen of Python about how "there should be one-- and preferably only one --obvious way to do it" is something that people all too often forget.

The zen of Python should be the zen of all languages.

Good thing we're not giving options for no reason other than to give options ;)