Our great sponsors
nushell | exa | |
---|---|---|
212 | 129 | |
29,864 | 23,271 | |
2.5% | - | |
9.9 | 3.2 | |
7 days ago | 18 days ago | |
Rust | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nushell
-
NuShell - Ceci n'est pas une |
These are just three small examples of what this shell written in Rust allows. The features are many and many more, but I'll leave it up to you to discover and enjoy them; I'm currently playing around with it and it's giving me a lot of satisfaction and immediacy, now it has a fixed place among the tools I use when working! The project is Open Source, so if you want to contribute, I invite you, as always, to do so, I leave you the link to the repo here!
- Xonsh: Python-powered, cross-platform, Unix-gazing shell
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
Any thoughts on fish as compared to nushell [0]? It's similar to PowerShell in its philosophy and is also written in Rust.
[0] https://github.com/nushell/nushell
-
jc: Converts the output of popular command-line tools to JSON
> In PowerShell, structured output is the default and it seems to work very well.
PowerShell goes a step beyond JSON, by supporting actual mutable objects. So instead of just passing through structured data, you effectively pass around opaque objects that allow you to go back to earlier pipeline stages, and invoke methods, if I understand correctly: https://learn.microsoft.com/en-us/powershell/module/microsof....
I'm rather fond of wrappers like jc and libxo, and experimental shells like https://www.nushell.sh/. These still focus on passing data, not objects with executable methods. On some level, I find this comfortable: Structured data still feels pretty Unix-like, if that makes sense? If I want actual objects, then it's probably time to fire up Python or Ruby.
Knowing when to switch from a shell script to a full-fledged programming language is important, even if your shell is basically awesome and has good programming features.
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
Maybe if the "popular" shells, but http://www.nushell.sh/ is looking better and better
- "<ESC>[31M"? ANSI Terminal security in 2023 and finding 10 CVEs
-
jq 1.7 Released
Yeah agreed, especially now that PowerShell is available cross-platform.
Nushell[1] also seems like a promising alternative, but I haven’t had a chance to play with it yet.
[1]: https://www.nushell.sh/
-
The Case for Nushell
I also discovered an existing discussion[1] related to this topic which includes a link[2] to a "helper to call nushell nuon/json/yaml commands from bash/fish/zsh" and a comment[3] that the current nushell dev focus is "on getting the experience inside nushell right and [we] probably won't be able to dedicate design time to get the interface of native Nu commands with an outside POSIX shell right and stable.".
[0] https://gitlab.com/RancidBacon/notes_public/-/blob/main/note...
[1] "Expose some commands to external world #6554": https://github.com/nushell/nushell/issues/6554
[2] https://github.com/cruel-intentions/devshell-files/blob/mast...
[3] https://github.com/nushell/nushell/issues/6554#issuecomment-...
I appreciate what projects like Nushell and Murex are trying to address, but having a saner scripting language and passing structured data in pipelines is not worth the drawbacks for me.
For one, Bash scripting is not so bad if you set some sane defaults and use ShellCheck. Sure, it has its quirks, but all languages do. Even so, the same golden rule applies: use a "real" programming language if your problem exceeds a certain level of complexity. This is relative and will depend on your discomfort threshold, but using the right tool for the job is always a good practice. No matter how good the shell language is, I would hesitate to write and maintain a complex project in it.
And for general QoL improvements with interactive use, Zsh is a fine shell, while still being POSIX compatible.
[1]: https://github.com/nushell/nushell/blob/main/crates/nu-comma...
[2]: https://github.com/nushell/nushell/issues/5027
[3]: https://github.com/nushell/nushell/issues/9310
-
Simple PowerShell things allowing you to dig a bit deeper than usual
I found nushell (https://www.nushell.sh) to be an impressive replacement "bash" for Windows
In terms of philosophy, think "Powershell but actually intuitive" : Every data is structured but command names are what you expect them to be. I usually don't even need to look at the documentation.
I liked it so much that I also replaced my shell on Linux with it, so I have the same terminal experience across all OSes
exa
-
A ‘Software Developer’ Knows Enough to Deliver Working Software Alone and in Teams
It depends on the scale of the project but man, if you can't build a simple CRUD app in your preferred stack and deploy it in some fashion (even if it's just a binary posted on some website, kinda like Exa) then that's just disappointing...
-
Which 2nd language should I learn?
Can compile to a single binary to build tools like exa
- Exa Is Deprecated
- ls -l IN COLOR!
-
What's your favorite Go architecture for a new micro-service? Here's mine...
Try https://github.com/ogham/exa and exa -T -L2 command . It will generate a good folder structure tree to update the question
-
macOS Command-Line Tools You Might Not Know About
Some of us don't want all of GNU's utilities; just on an as-needed basis. They're not as needed as they once were.
Many of these utilities have been rewritten in Rust and have more modern features.
For example, instead of ls, I use exa [1]. Or ripgrep [2] instead of grep.
[1]: https://github.com/ogham/exa
[2]: https://github.com/BurntSushi/ripgrep
-
List of apps I use every day - Version 2023
fish: A very fast shell with various customization options to streamline daily commands. I discovered it through this post by @caarlos0, where he provides more details about performance and the differences between fish and zsh. Additionally, I use some CLI utilities like delta, exa, and ripgrep. Here's my dotfiles for fish.
-
Ls with icons
Hi! I use this: https://the.exa.website, and the package to this: https://archlinux.org/packages/extra/x86_64/exa/
-
Everything I Installed on My New Mac
I still use exa for listing files in the terminal. It's a modern replacement for ls with a lot of useful features. With icons, colors, and git integration, it makes listing files much nicer.
What are some alternatives?
fish-shell - The user-friendly command line shell.
lsd - The next gen ls command
elvish - Powerful scripting language & Versatile interactive shell
colorls - A Ruby gem that beautifies the terminal's ls command, with color and font-awesome icons. :tada:
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
PowerShell - PowerShell for every system!
fd - A simple, fast and user-friendly alternative to 'find'
alacritty - A cross-platform, OpenGL terminal emulator.
coreutils - Cross-platform Rust rewrite of the GNU coreutils
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
bat - A cat(1) clone with wings.