busybox-w32
nushell
busybox-w32 | nushell | |
---|---|---|
16 | 213 | |
640 | 29,963 | |
- | 1.3% | |
9.2 | 9.9 | |
6 days ago | 6 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | 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.
busybox-w32
- The Awk Programming Language, Second Edition
-
POSIX sh is a better interpreter than python
Even in environments such as win32, we have https://frippery.org/busybox/ that is just fucking awesome. Staying the size below an 1mb while being extremely fast. Unlike the shitty python package which has 40mb archive size and leave breadcrumbs for me to cleanup all over my filesystem.
-
The amount of times I have accidentally done this...
Win32 port is here: https://frippery.org/busybox/
-
God's developer console
Look into busybox for windows https://frippery.org/busybox/. Pretty bad ass even with it’s downsides of missing applets and such
-
Does vim suck on windows?
Vim by itself means no supporting unix environment. It's useful to call out to powerful external tools not present by default on Windows. I fill that gap with busybox-w32. It's not a big deal once solved.
-
looking for a graphics library
Sure, it's not necessary, but a few simple, nice tools (<600kiB for an entire suite of extended unix utilities) makes thing a whole lot simpler on a platform devoid of nice tools.
-
Compress lots of files into lots of individual files?
To operate on many files you'll need better tools than what Windows gives you. One option is busybox-w32 (important caveat: doesn't support unicode paths), which will get you some basic command line tools. For example, to gzip compress every file under the current directory, including subdirectories (leaving the originals behind with -k):
-
Windows verison of cal
busybox-w32 includes a cal applet. If that's all you care about, you can just rename busybox.exe to cal.exe.
-
What's in your tool belt?
busybox-w32: standard unix utilities for Windows. It's a BusyBox port.
-
Makefile example project for Windows with source, include, libs and build folders. Also with a detailed explanation!
IHMO, even better is to just use POSIX sh in your Makefile and simply make it a build requirement. It's easy to obtain a reasonable sh even on Windows (Cygwin, MSYS2, busybox-w32), and to further support exactly this I include sh alongside make in my development kit distribution. This uniformity lets me hit all operating systems with the same Makefile. I use EXE from the environment to determine the binary file extension, if any.
nushell
-
PowerShell: The object-oriented shell you didn't know you needed
I rather nushell for this purpose, it's more fun to write and easier to read.
https://www.nushell.sh/
-
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
What are some alternatives?
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
fish-shell - The user-friendly command line shell.
notty - A new kind of terminal
elvish - Powerful scripting language & Versatile interactive shell
oursh - Your comrade through the perilous world of UNIX.
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
csvinfo - A small util to show max column lengths for a passed CSV file.
PowerShell - PowerShell for every system!
csvquote - Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines
alacritty - A cross-platform, OpenGL terminal emulator.
awk - Random AWK code
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.