opam is a source-based package manager. It supports multiple simultaneous compiler installations, flexible package constraints, and a Git-friendly development workflow.
the bit that talks about the equivalent of the eval $(opam env) command is bigger than on unix and thus less readable
the question about selecting another shell seems confusing during opam init. It doesn't say what are the drawbacks or what it's going to be used for. Also it's asked after a message about the current shell has been displayed, which can add to the confusion.
From this discuss post (https://discuss.ocaml.org/t/windows-compiler-support-in-opam-2-2-0-beta2/14648/3), there are a number of unintuitive things in
opam initthat we could polish:eval $(opam env)command is bigger than on unix and thus less readable