Kudos for writing something in rust and not appending "written in rust!" everywhere.
Why is everything written in rust nowadays? Apart from the safety it provides.
GitHub – nushell/nushell: A new type of shell
11–20 of 411 posts
Re: GitHub – nushell/nushell: A new type of shell
#12Kudos for writing something in rust and not appending "written in rust!" everywhere.
Why is everything written in rust nowadays? Apart from the safety it provides.
Good package manager, broad ecosystem of packages, no header files, helpful compiler messages. It offers a good alternative to C++ for native applications.
Re: GitHub – nushell/nushell: A new type of shell
#13Test it with Casey Muratori's benchmark: https://github.com/cmuratori/termbench
Context: https://twitter.com/cmuratori/status/1401761848022560771
Re: GitHub – nushell/nushell: A new type of shell
#14This 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.)
Re: GitHub – nushell/nushell: A new type of shell
#15Seems 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.
Re: GitHub – nushell/nushell: A new type of shell
#16Re: GitHub – nushell/nushell: A new type of shell
#17When 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
Re: GitHub – nushell/nushell: A new type of shell
#18Earlier quoted context omitted.
Why is everything written in rust nowadays? Apart from the safety it provides.
Good package manager, broad ecosystem of packages, no header files, helpful compiler messages. It offers a good alternative to C++ for native applications.
Not to mention excellent support for algebraic datatypes and pattern matching.
Re: GitHub – nushell/nushell: A new type of shell
#19Very 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.
Re: GitHub – nushell/nushell: A new type of shell
#20Kudos for writing something in rust and not appending "written in rust!" everywhere.
Why is everything written in rust nowadays? Apart from the safety it provides.
I think Cargo doubling as both build tool and package manager is a big factor here. The combination of Cargo + crates.io makes it very easy to write some Rust code and make it available to anyone with Cargo on their system. Either by `cargo install nu` to build it from sources on crates.io or `cargo install` inside the git repo to build my own customized version. No more waiting for distro packagers to keep up.
Putting this together makes for a nice environment to distribute native system tools. And in the last few years we've seen a wave of these tools becoming popular (ripgrep, bat, fzf, broot, exa and some others).