There are tons av resources (scripts, guides, examples) that make up the backbone of a lot of IT departments.
If you’re setting a new organisation, you can chose to go with nushell, but then you have to accept that you either need to write all scripts from scratch, or you need to convert an existing script to nushell. If you put nushell into an existing department/organisation, then you face the same problem.
Before there are substantial resources to solve common sysadmin tasks in nushell, organisational adoption is unlikely due to the cost.
How many scripts get re-used outside of the org, though?
There are tons av resources (scripts, guides, examples) that make up the backbone of a lot of IT departments.
If you’re setting a new organisation, you can chose to go with nushell, but then you have to accept that you either need to write all scripts from scratch, or you need to convert an existing script to nushell. If you put nushell into an existing department/organisation, then you face the same problem.
Before there are substantial resources to solve common sysadmin tasks in nushell, organisational adoption is unlikely due to the cost.