• As much as I want to champion nushell, the problem is that it isn’t available on every machine like traditional shells.

    That means my whole organisation need to have nushell installed on every machine, and even then, any scripts using nushell is effectively useless outside the organisation.

      • 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.

  •  hedy   ( @hedy@lemmy.sdf.org ) 
    link
    fedilink
    English
    1
    edit-2
    2 months ago

    Yes, really. fi and esac are a joke that never found their end. No one would design a language that did that with a straight face these days.

    Well, I thought that was genius when learning Bash.