95 ms·
GitHub – nushell/nushell: A new type of shell
- purplecats 5y agoThis looks pretty awesome. Wonder if it could be used with a command rather than as a new shell. Tangent: How is this at the top of the front page with a dozen upvotes and no comments? Maybe these upvotes all occurred at once?
- tastroder 5y agoThis tracker was a show HN last month, looks pretty normal https://upvotetracker.com/post/hn/27525031 https://upvotetracker.com/post/hn/27525031
- spoiler 5y agoOn one hand I do like the idea that it's a shell since it means in it's nicely integrated with itself (can't think of a better phrase), but on the other hand it's also what's making me a bit reluctant to seriously consider it because I'm too used to fish. It would be ideal to me if it were a tool that could be piped into. However, that's not to say I won't at least give it a try these days, since I'm really curious about it.
- deleted 5y ago[deleted]
- sam0x17 5y agoA lot of people just upvote anything that is a GitHub repo because it's generally more useful than actual news
- brundolf 5y agoIt's not uncommon for people to upvote without commenting if they don't have anything to actually add or the post is self-explanatory
- Macha 5y agoSoftware releases commonly get this treatment, I remember the comment about why there was no discussion on the actual contents of the change on a decently upvoted post about a minor release of wine, for example.
- vbsteven 5y agoYou can with `-c`: $ nu -c "sys | get host.name" > Ubuntu
- jamincan 5y agoI will sometimes upvote something without comment if I found it interesting, don't really have anything useful to say myself, but would be interesting in seeing what other people have to say.
- shric 5y agoKudos for writing something in rust and not appending "written in rust!" everywhere.
- bmlzootown 5y agoIt's the new "I use Arch btw". Genuinely kind of tired of it already.
- iFreilicht 5y agoMeh, not really. Something being written in Rust is a feature to me.
- geodel 5y agoThanks for letting us know :)
- firefly284 5y agoWhy is everything written in rust nowadays? Apart from the safety it provides.
- skocznymroczny 5y agoGood package manager, broad ecosystem of packages, no header files, helpful compiler messages. It offers a good alternative to C++ for native applications.
- chalst 5y agoNot to mention excellent support for algebraic datatypes and pattern matching.
- kamray23 5y agoADT and pattern matching really does it. Older languages certainly have their pull and can do a lot but with many modern coders having an interest or even education in higher level mathematics, easily being able to do that will put you way ahead of the competition. Even the hyper-pure Haskell now runs its own ecosystem and has actual systems written in it.
- dmitriid 5y agoTest it with Casey Muratori's benchmark: https://github.com/cmuratori/termbench https://github.com/cmuratori/termbench Context: https://twitter.com/cmuratori/status/1401761848022560771 https://twitter.com/cmuratori/status/1401761848022560771
- HajiraSifre 5y agoThat program is for testing terminal emulators, not shells.
- dmitriid 5y agoAh, true. Got confused there.
- rincebrain 5y agoThis feels extremely like PowerShell, from all the examples, and even cites "draws inspiration from projects like PowerShell", so "a new type of shell" feels very disingenuous unless it has additional novel properties that aren't evident just from these. There's also no support for variables yet if the page is to be believed, which means there's 0 chance of me using this for more than 5 minutes right now. (I'm not trying to say this project isn't worthwhile, just that many other people in the thread currently seem to be entirely uncritical.)
- gexla 5y agohttps://github.com/nushell/nushell#progress https://github.com/nushell/nushell#progress "Nu supports variables and environment variables"
- rincebrain 5y agoThat page was edited an hour ago, so that was presumably a stale example. I'm glad to be wrong!
- jupp0r 5y agoHave you used PowerShell much? The examples in the Readme make it obvious that it's very different (in a good way).
- rincebrain 5y agoI use PowerShell daily, though I do not, for example, develop nontrivial modules for it. Could you provide an example of what I'm overlooking?
- brushfoot 5y agoI use PowerShell extensively, and there are no significant differences in the README examples. They're basically rebranded PowerShell statements. I see minor syntax differences, for example in the comparison operators. Nothing that would it would be worth losing the .NET BCL or PowerShell's cmdlets for.
- 5y ago
- stinos 5y agoSeems pretty well designed. Though the decision to be able to refer to the properties of data in a pipe directly with their names might cause some confusion in the end (the 'size' in 'ls | where size > 1'). Ok it's succinct, but it's also a bit weird that the loop variable (what this basically is in a pipe) is treated different than all others. Not that e.g. PS' $_ is so great, but at least it's obvious: it's a variable just like all others.
- chalst 5y agoThis is a feature that Powershell gained and it is very useful.
- pama 5y agoWhen I think of a new shell I want to understand quoting and the special meaning of characters. Bash has found a decent compromise; what does nu plan to do? The documentation is pretty scant, but perhaps that’s because the language is still developing: https://www.nushell.sh/book/types_of_data.html#strings https://www.nushell.sh/book/types_of_data.html#strings
- yetanother-1 5y agoVery promising project that I hope it will take off and succeed. I recently switched to zsh with the addition of oh-my-zsh and I am happy how it has features like auto completion and command validation of some sort, but this could take it to the next level. I am just afraid to change to it and be disappointed about some incompatibility issues or bugs / crashes. I will observe and wait until it's quite popular to hop on I think.
- Offpics 5y agoTry fish shell. It has auto completion by default and is easy to configure with web interface "fish_config", no need to rely on some community repo like oh-my-zsh. There can be bugs if you set it as default shell but i just append "fish" at the end of my .bashrc :)
- ar_lan 5y agoIt's so interesting - it seems that fish is getting more and more popular lately. I tried it ~7 years ago and thought it was severely lacking, so I just stuck with zsh and have never really had a reason to look back. Maybe I'll check out fish again at some point - what features does it have that drew you to it?
- drcongo 5y agoAlmost everything that you might get from oh-my-zsh is built in and it's _much_ faster. I've been using Fish for a few years now and I love it.
- ar_lan 5y agoI don't really use `oh-my-zsh`, I just built my own prompt. It's pretty snappy, so I don't feel a huge need to switch, but maybe on a slow day I'll install fish to give it a whirl.
- clashmeifyoucan 5y agonot OP but the two features of fish that stood out for me so much that I make it my default shell on remote servers are 1) the autocomplete suggestion as you type a command [1] 2) scrolling thru commands after partially writing one only shows entries that match the written text 3) knowing if a command will work before pressing enter -- saves from a lot of gotchas. all of these read like features nice to have but not essential, but when you're using something every day, it's worth it :) [1]: https://fishshell.com/docs/current/tutorial.html#autosuggestions https://fishshell.com/docs/current/tutorial.html#autosuggest...
- darepublic 5y agoIt would be nice if the syntax could be very forgiving. So typing something such as 'show me the files over 12 mb' would work. Initially when I read the README it's what I thought it was.
- hyperpallium2 5y agoNeed some description up front, not in the 5th section ("Philosophy" https://github.com/nushell/nushell#philosophy https://github.com/nushell/nushell#philosophy). Some ideas: "powershell for unix", "structured pipes", "pre-parsed text", "small, useful, typed tools loosely coupled."
- jupp0r 5y agopowershell for unix is ... powershell: https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-linux?view=powershell-7.1 https://docs.microsoft.com/en-us/powershell/scripting/instal...
- anticodon 5y agoPowerShell from Microsoft is looking too alien on Unix. Just looking at the syntax I already feel uncomfortable. It's hard for me to criticize it because I haven't used it, but it looks like it was designed by a committee and overdesigned. I.e. it wasn't created from the need, like someone at Microsoft wanted to automate his work and created PS to solve his problem. It looks like some boss decided: "They have shells, so we should have it also. But we will make it much cooler. So, let's gather a committee of 500 of our best managers and let's decide what features it should have". It looks artificial and inconvenient to me unlike Unix shells. Maybe I'm wrong. But I'm pretty sure that even syntax of PS makes it harder to type the commands. Unix commands are very short (many are 2-4 letters long), all lowercase and do not contain characters which are hard to type (e.g. `-`).
- helsinkiandrew 5y agoI wonder if the pipelining could be added to a regular shell to get its advantages - the cost for me from moving from Bash is too high. Basically a "cols" command on steroids - making that have some kind of context aware column names (I'm not sure how) and then support expressions would make it work in any shell.
- chubot 5y agoThat's basically what Oil's approach is. Oil is POSIX and bash compatible, but it also has Python-like data structures (recursive dicts, lists). And there's also room to add select/filter/sort. We need help :) https://github.com/oilshell/oil/wiki/Structured-Data-in-Oil https://github.com/oilshell/oil/wiki/Structured-Data-in-Oil
- imperialdrive 5y agoHeck yah - Very NICE! The demo is what hooked me.
- deleted 5y ago[deleted]
- calltrak 5y agoFound this handy git cheat-sheet https://picc.io/p/xM2wenl.png https://picc.io/p/xM2wenl.png
- kayman 5y agoSimilar to "bourne shell" and "bourne again shell" aka bash I can see the evolution now. "nushell". Next iteration: "nuer shell" (newer) or "renushell" (renew)
- lta 5y agoI stopped reading at "rather than thinking of services and input as a stream of text", horrified. Why would we do that ? KISS !
- heinrichhartman 5y agoBy the same reasoning: Would you not use databases because they have a schema? or JSON...? Heck, even utf-8 could be too complicated.
- lta 5y agoYou have a point. That sounded like pure conservatism, and to some extent it is. But still, text is simple and that what makes shell powerful, trying to move to higher level abstraction is has a chance to create fragmentation and break the solid foundations on which Unix is built.
- jbverschoor 5y agoBecause parsing text is shit. Good luck AWK'ing everything. Datastreams are simple.
- lta 5y agoIt's often better than trying to figure out the weird formats all the tool would use otherwise
- jbverschoor 5y agoSo start outputting something like json. And render it in the console as an ascii table
- AprilArcus 5y agoI wonder if this could be accomplished in a more general way with a fourth standard file descriptor for structured data. stdjson basically.
- tgv 5y agoA pipe only conveys stdout. You could redirect 4>&1 1>/dev/null, but you'd have to rewrite all tools to generate both stdout and stdjson anyway.
- oarsinsync 5y ago> You could redirect 4>&1 1>/dev/null For anyone confused by this, 1 is the output to stdout, and 4 is being redirected to where 1 goes, which is stdout. Unrelated to that, 1 (what’s actually being output to stout by the application) is being redirected to /dev/null. The order of operations matters. If 1 was redirected to /dev/null first, then 4 would also end up in /dev/null. As it stands now, that doesn’t happen.
- tgv 5y agoGood one. I did look it up before I posted, too. I’m never 100% sure.
- im3w1l 5y agoSo you are supposed to read it from right to left? "First take 1 and throw it away. Next put 4 in 1." Is that how it works?
- kubanczyk 5y agoNot quite. Left to right: copy the descriptor 1 onto descriptor 4, change descriptor 1 to result of open("/dev/null"). The >& is for copying the descriptor not for aliasing ("hardlinking") it. The descriptor is the "fd" argument, e.g.: write(int fd, const void *buf, size_t count)
- vultour 5y ago
- lsllc 5y agoSort of looks like a modern take on VMS!
- sime2009 5y agoI played with it recently. The interactive part is limited at the moment, but I really like the idea of having operations like sorting and filtering separate from the tools which produce the data. Having these things consistent and available everywhere is a huge cognitive win. I can finally sort and filter `ls` output without having to read the man page. :) "Querying" data feels a lot like SQL in that respect.
- bawolff 5y agoWere you not able to before? ls | grep foo | sort is hardly something people normally read the man page for.
- rnestler 5y agoThis isn't the way I'd sort ls output by date or whatever field. I'd use `ls -l --sort=date` which I guess is what the GP meant with having every tool do their own sorting by field. In nushell one can just do `ls | sort-by size`
- kaba0 5y agoNow sort by filesize
- rkeene2 5y agoFile size or file length ?
- the_biot 5y agoNushell missed the one feature that every Unix shell has: if it doesn't recognize the first word as a built-in command, look it up and run it as an executable. It's crucial, and nushell is missing out on an ecosystem of random shell commands to complement it as a result. This, of course, is what makes the Unix shell so great: the many little programs able to work together via pipelines. This makes nushell an interpreter command line, instead of a system shell. (Yes, you can "escape" by typing ^ before a word. That's not nearly the same thing.)
- jntrnr 5y agoThis is how Nushell works. If the command isn't an internal command, it will run it from you path. Curious what you tried that didn't work.
- bennyp101 5y agoIts the 2nd paragraph "If a command is unknown, the command will shell-out and execute it (using cmd on Windows or bash on Linux and macOS), correctly passing through stdin, stdout, and stderr, so things like your daily git workflows and even vim will work just fine."
- the_biot 5y agoArgh, how did I miss this. The ^ is just for overriding built-ins with external executables. Apologies! Clearly I hadn't tried nushell -- this feature I thought missing was a big no for me. I have now, and this is definitely worth a try. Thanks all!
- tomduncalf 5y agoLooks pretty cool. Anecdotally, I found switching shell to be more of a challenge than expected - I’ve been using (oh-my-)zsh for years and decided to try fish, but all the little differences were too annoying for me to get used to - I guess you build up a lot of “muscle memory”! That said, I probably just use the same commands most of the time. If you were doing more advanced stuff maybe it makes more sense to invest the time
- silentguy 5y agoI think you can achieve most of the fish features in zsh with the help of plugins. The most compelling feature of fish was history substring search. You type something, press up button and you get a command in history with that substring. I used 'history-substring-search' plugin to achieve that. There are also 'syntax-highlighting' and 'completion' plugins which bring fish shell features to zsh. I use prezto for its speed after getting annoyed by oh-my-zsh slowness.
- tomduncalf 5y agoGood tip, thanks!
- colourgarden 5y agoThe title is somewhat misleading and makes it seem like this is a GitHub company initiative rather than a project just hosted on GitHub. I've not seen this title format on HN before. Could it be changed?
- jtokoph 5y agoThe title is the actual value of the title html tag on the page
- roblabla 5y agoHeh, that's interesting: When you're logged in, the title tag changes to drop the "GitHub -" prefix.
- tim-- 5y agoSEO strikes again!
- foobar33333 5y agoConsidering people often search 'github project name' it probably makes sense.
- corobo 5y agoIt could go at the end just as easily like every other site though
- hibbelig 5y agoI think the "nushell/nushell" part makes it clear which repo it is talking about.
- cbolton 5y agoI didn't find it clear, I also thought it was a GitHub project.
- andix 5y agoI never really got acquainted with PowerShell. It always felt very clunky to me. But it exists, it's mature, it's cross platform and widely supported. Maybe I should give PowerShell Core a try.
- xiaq 5y agoShameless plug: if you're interested in nushell, you might also be interested in Elvish: https://elv.sh https://elv.sh (And the various other new shells, documented by the author of another new shell, Oil: https://github.com/oilshell/oil/wiki/Alternative-Shells https://github.com/oilshell/oil/wiki/Alternative-Shells)
- simonjgreen 5y agoOn the face of it this looks like powershell
- Tepix 5y agoThis seems like a missed opportunity to call it "nutshell"!
- j1elo 5y agoThinking this is so cool! I was wondering if seriously buying into an alternate shell like this would be worth it in the long run. Would really love to read from people who use(d) an alternative shell, both success and failure stories. I cannot shake from my head the idea that buying into a non-standard shell will only work for personal projects in one's own workstation, but it won't fly too far for company work because you'd then be introducing an implicit dependency on your special snowflake non-standard runtime. Which is something we came to accept and assume for interpreted languages (Python, Ruby, Node, etc.) but I'm not yet ready to assume for shell scripts. So right when I was going to test Nushell, I discover there are also other shells like Elvish [0] and Oil which supports structured data [1]. Now on top of my hesitations I'm adding decision paralysis :-] [0]: https://elv.sh/ https://elv.sh/ [1]: https://www.oilshell.org/ https://www.oilshell.org/ Lots more shells: https://github.com/oilshell/oil/wiki/Alternative-Shells https://github.com/oilshell/oil/wiki/Alternative-Shells
- maccard 5y agoI tried fish for a while. The differing syntax between fish and bash for fundamental things mean I was running all my scripts through bash anyway, and if I wanted to share them/use them elsewhere in the company it had to be bash, so I swapped back to bash.
- okamiueru 5y agoIf you're running scripts, what difference does it make that you use fish? You're not really supposed to write scripts for fish, unless it is meant to be used be the fish shell itself. A shebang on the top of your script will invoke the script with the right executable, and whether you called it from bash, zsh or fish would make no difference.
- toxik 5y agoSo, instead of just typing shell commands, you type something else, but as soon as you need a shell script, you have to go back to shell commands.... Why not just cut out the middleman?
- lloydatkinson 5y agoIt's basically powershell
- Andy-AO 5y agoWhat is better about this tool than PowerShell? The README doesn't mention it at all, just that the tool is inspired by PowerShell.
- majkinetor 5y agoNothing. Lets be realistic. Even if it goes mainstream it will be decade behind PowerShell in conceivable future. While I appreciate the enthusiasm for developing shell, nothing usable here in years to come IMO when I can just use pwsh.
- mukadul 5y agoWill fork it as nutshell
- akavel 5y agoCould someone let me know if https://github.com/akavel/up https://github.com/akavel/up works ok with it? (on Linux or Mac or WSL) I'd be grateful for feedback!
- eatonphil 5y agoIt's such a huge pain to set up bash on windows (it worked fine, very easy on one laptop but I cannot get bash or wsl working on another newer laptop) that I wrote a very basic wrapper for shell scripts that will transform arguments of Linux user land (like cp, mv, rm) to their windows equivalent. This way all you need is python and your "bash" scripts can just work. Sorta. There are a lot of edge cases. But at least it works enough that I can stop trying to figure out how to install bash on windows or what's wrong with my laptop.
- hans1729 5y agoI installed wsl on like 10 machines, including "newer laptops", and never had problems with the setup. Instead of solving your actual problem you created a whole new problem domain, that seems... not like the way to go
- eatonphil 5y agoThe "domain" I care about is for basic build scripts to work on Windows and Linux. Whichever way gets me back to regular work is the best way! I do not have the experience to debug when BoW or WSL do not work unfortunately.
- cerved 5y agowhile it can be a pain to deal with windows quirks, writing a wrapper script to deal with low level file IO stuff sounds like a good way to open a whole can of worms and irrevocably mess up your whole system
- mkl 5y agoWhat was the problem with WSL? It's been trivial to install on every machine I've tried: work, personal, old, new, upgraded from Windows 7, local account, Microsoft account, etc.
- eatonphil 5y agoYes I had that experience until this one laptop, ironically it's a surface laptop. Most likely I screwed some setting up but now no tutorial for bash in windows or wsl works anymore and I have no idea how to work around.
- larodi 5y agothere's fair amount of comments here (and in other similar posts) which read like: 'nushell is basically a powershell something' 'bash/zsh is better/worse than pwsh/etcshell' this is very unfair because pwsh allows control over of the all .NET/COM+ available in a system (well, .NET Core only on non-MS, but still). while nushell stands on its own shoulders or if u like - allows control of other programs executed, but would not easily call into any API that is a language-specific one nor parse its output as structured one. so when comparing bash, zsh, nushell, pwsh one should take into consideration that these have different foundations and goals even. like perl stands on top of CPAN, all the JVM stuff on top of all classes, etc. although it is difficult to say why no one has created (to my knowledge) reasonable JVM-based shell, nor a python-based-one, since java targets such a large number of OS/platforms and provides such a broad library. perhaps because people assume that a shell program should follow the UNIX concept of one-program-does-one-thing-only. on the contrary - it would be a killer feature to have nushell be able to natively execute java/python/whatever API calls and use the structured output (like pwsh indeed). in essence - is very limiting to compare bash to pwsh only in the sense of 'how much can be done with only few characters', because this always leads to very opinionated and biased arguments and eventually discussions taken out of context.
- iib 5y ago@joseph8th mentioned a shell [1] earlier, that at least at first glance, seems to be a python + bash combination, similar to what powershell does with .net. [1] https://xon.sh/ https://xon.sh/
- deleted 5y ago[deleted]
- gavinmckenzie 5y agoIt looks very interesting, but the first thing I noticed as a macOS user, is the shell has a built-in command "open" which I expect will conflict with the standard macOS command "open" and I haven't found any docs that describe how to deal with this.
- __d 5y agoThis is true of shell built-ins for eg. test too. The solution is to use the full path if you want to use the program, not the shell built-in. In this case, "/usr/bin/open" not "open" will get you the macOS utility. If you get sick of doing that, create a shell alias.
- ajeetdsouza 5y agoShameless plug: zoxide recently added support for Nushell. It's a smarter cd command for your shell (similar to z or autojump). https://github.com/ajeetdsouza/zoxide https://github.com/ajeetdsouza/zoxide
- michael-ax 5y agoseems nu can do a lot of otherwise horrid sed/awk/cut/etc parsing for bash. that is great!
- debacle 5y agoThis seems very similar to powershell, with far better syntax.
- ilyash 5y agoShameless plug: https://github.com/ngs-lang/ngs https://github.com/ngs-lang/ngs - Next Generation Shell Compared to other modern alternatives, NGS is "programming language first". Repository of scripts written in NGS, aptly named "NGS Scripts Dumpster" - https://github.com/ngs-lang/nsd https://github.com/ngs-lang/nsd
- arupy 5y agoI use this in combination with fish shell and it's been working really well. I can just switch over to `nu` when the task merits; no need to replace my current shell. I can also just run a one-off line like this. nu -c "ls | where size > 10b"
- augstein 5y agoHow does it compare to fish shell (especially fish’s great autocompletion), e.g. why are you not switching completely?
- arupy 5y agonu is still in its infancy, and currently lacks critical features of other shells, which is why I haven’t switched completely. As for the future, perhaps a bit brazen, but I’m confident that other shells will introduce the core feature of nu in the near future to stay competitive. I can see fish having a “||” operator and rewrites of a few gnu functions to achieve what nu does natively.
- xpe 5y agoI see the value proposition of nushell. I'm wondering if I should also try fish. May I ask if you switched to fish from zsh? What motivated your change? Background: I invested some time not too long ago to read zsh docs in detail and customize my own configuration (e.g. instead of using oh-my-zsh). Since then, I've been quite happy with zsh. That said, I'm also open to switching to fish and/or nushell based on recommendations.
- sahkopoyta 5y ago> what motivated your change? didn't switch from zsh but bash, did it because wanted a bit more features at shell without additional configuration
- arupy 5y agoI didn’t switch from zsh, but from bash, to fish, primarily because bash was occasionally a bit clunky to use, and there were a lot of things that could be optimized in a modern environment. I settled on fish because it suited what I was looking for: an ergonomic shell that worked well out-of-the-box. Paired with strong community support, clean scripting syntax, and a wide ecosystem, it makes for a really enjoyable shell experience. I haven’t tried zsh, so I can’t compare the two. I’m happy with fish, and I don’t see much benefit to switching to nu. nu is exceptionally good at one thing: working with data, but lacks features in other areas (auto-completion, scripting, etc.). With time, I can see these features being implemented, but I think they’ll be re-inventing the wheel in a lot of areas that other shells are already good at.
- stackedinserter 5y agoWhat if we added json output mode to all shell commands? Or at least make some wrappers that parse their unstructured text output into json. We would be able to use standard pipelines and jq to filter/query outputs, without any custom shells. Just imagine: ifconfig --json | jq '.[] | [.interface, .inet] | @tsv'
- talideon 5y agoYou're not the first person to think of that. See Juniper's libxo: https://github.com/Juniper/libxo https://github.com/Juniper/libxo It's integrated into a lot of FreeBSD's command line tooling, and is very useful, when it's available.
- edwinyzh 5y agoSo a lot of FreeBSD command line tools support JSON output? That's cool! And I wish it was linux...
- dmytrish 5y agoThere is some movement in this direction: e.g. it's possible to do `ip -j addr` today.
- e12e 5y agoI am with you in principle - but I still don't get the jq path/filter syntax I'm afraid. I think I'd vastly prefer map/reduce/zip commandlets... Ed: I'd say from a quick glance that I think I rather prefer nushell to powershell
- luke2m 5y agoI use fish for general use, but still write all my scripts with bash. It has worked very well for me.
- est 5y agoThat brings a WMI vibe.
- silentguy 5y agoWhat's WMI? Google search says https://docs.microsoft.com/en-us/windows/win32/wmisdk/wmi-start-page https://docs.microsoft.com/en-us/windows/win32/wmisdk/wmi-st... but I doubt you were talking about that.
- est 5y agohttps://docs.microsoft.com/en-us/windows/win32/wmisdk/invoking-a-synchronous-query https://docs.microsoft.com/en-us/windows/win32/wmisdk/invoki...
- xpe 5y agoThe philosophy section is the most important aspect, in my opinion, because I want to know why I should switch. In other words, show me a better future, and then I'm more likely to try it out. > Philosophy > Nu draws inspiration from projects like PowerShell, functional programming languages, and modern CLI tools. Rather than thinking of files and services as raw streams of text, Nu looks at each input as something with structure. For example, when you list the contents of a directory, what you get back is a table of rows, where each row represents an item in that directory. These values can be piped through a series of steps, in a series of commands called a 'pipeline'.
- jpz 5y agoFirst 60 second impression - this looks like powershell with not-insane syntax. Looks quite revolutionary, it breaks the traditional paradigm for UNIX shells and appears to artfully refine the good concepts in Powershell (which seem to be let down severely - in my opinion - by UX issues.)
- alkonaut 5y agoWhat's wrong with the powershell syntax? The long names? Those are optional. I find the idea of short names (for interactive) AND the option of long names very good. Many of these aliases are similar to unix commands (e.g. "cat" instead of Get-Content or "ls" instead of Get-Childitem).
- ofiryanai 5y agoOn top of the nice approach to structured output with pipelines, the "cross-OS first" approach is amazing! Very cool to use a modern shell that can fit both Windows and Unix by design (and not through WSL), hell I'm going to try to introduce it to my small company as a standard tool. Hope it's not in a too immature stage, however it looks very shining and promising considering the enthusiast contributors community. I'm in
- thefunnyman 5y agoFunny enough, the new PowerShell fits this description too now that it’s packaged for Linux.
- rdudekul 5y agoHere is a recent video on Nushell 0.32 features: https://www.youtube.com/watch?v=AqYxhJKblvY https://www.youtube.com/watch?v=AqYxhJKblvY
- korse 5y agoI don't get these sorts of efforts. 'Let's make something complex appear intuitive by adding more complexity'. I really respect the work that has gone into this project, but no thanks.
- johnfn 5y agoBut that can work. Just look at Google: massively complex product and problem, but sure appears pretty simple to the layman - I just type some words into the box and hit enter!
- moocowtruck 5y ago"A nu type of shell"
- xolve 5y agoIts not as yet feature complete but has come a long way from its earlier beginnings. I have been using it on Windows and being native and close to UNIX shells really helps my workflow. The inbuilt commands and structured philosophy is a great approach.
- unixhero 5y agoNushell is a new shell. In a nutshell, nushell handles pipes like powershell in a structured data type instead of a string/stream based pipe.
- citizenpaul 5y agoMy issue with these types of things is always the same. Awesome it does all this stuff I love it, I use it everywhere. Dev: I have decided to stop working on this project thanks for all the support. If anyone wants to take ownership of it I am willing to transfer its ownership. (Crickets) Me now after using it for a couple of years have to go back to standard bash or whatever and now people think I have no idea what I'm doing since I forgot so much stuff from lack of daily use.