Reasons for Non-Adoption and Discontinuation of Nushell

4th chunk of `blog/2019-11-23-nushell-survey-results.md`

d83f093f9f9b76c5b9931c739ee366127530739126b0c7890000000100000502



We also asked for feedback from people not using Nu what their thoughts were. What are the kinds of things that block them from using Nu?

Top of the list are "time" and "maturity". Many people mentioned that it takes time to learn a new system, and time is a precious resource (don't we know it!). Maturity also came up for a lot of folks - if it's not mature yet, the time investment might go to waste. In general, there was a sense of waiting until things are further along before jumping in.

We also heard from many people who were perfectly comfortable in their current shells, whether it be zsh, bash, or fish. For these responders, Nu doesn't offer a compelling reason to switch, yet.

### Quotes

- _"I'm very invested in bash already, but I love the concept and the work being done."_
- _"Too comfy with the current shell, also I am lazy, but the project is awesome"_
- _"I don’t transform data in the shell much, so the core value proposition of nu shell doesn’t resonate well with me."_
- _"I know a lot about traditional shells and don't want to re-learn how to do all that in nushell"_

## Used Nu but stopped (38 responses)

Title: Reasons for Non-Adoption and Discontinuation of Nushell

Summary

The primary reasons people aren't using Nushell are lack of time to learn it, concerns about its maturity, and comfort with existing shells like Bash, Zsh, or Fish. Some feel Nushell's value proposition doesn't resonate with their needs. Former users stopped due to issues with maturity, lack of time, not needing it, and deficiencies in features like auto-completion, aliases, scripting, and documentation.