cuezel
busybox-w32
cuezel | busybox-w32 | |
---|---|---|
1 | 16 | |
12 | 642 | |
- | - | |
0.0 | 9.2 | |
about 3 years ago | 8 days ago | |
Go | C | |
- | GNU General Public License v3.0 or later |
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.
cuezel
-
Dagger: a new way to build CI/CD pipelines
I played with a similar idea a while ago: https://github.com/ecordell/cuezel/ (cuezel as in: "Bazel but with CUE"), but I was never sure that what I was doing was in the spirit of CUE.
CUE pushes nondeterminism into "_tool.cue"[0] files that are allowed to do things like IO and run external processes. Tool files scratch a similar itch to Makefiles, but they lack an integrated plugin system like Bazel (hence why I played with the idea of CUE + Bazel).
With Dagger you seem to be restricted to the set of things that the dagger tool can interpret just with like my Cuezel tool you are limited to what I happened to implement.
In CUE `_tool` files you are also limited to the set of things that the tool builtins provide, but the difference is that you know that the rest of the CUE program is deterministic/pure (everything not in a _tool file).
There's clearly value in tooling that reads CUE definitions, and dagger is the first commercial interest in CUE that I've seen, which is exciting.
But I'm most interested in some CUE-interpreter meta-tool that would allow you to import cue definitions + their interpreters and version them together, but for use in `_tool` files to keep the delineation clear. Maybe this is where dagger is heading? (if so it wasn't clear from the docs)
[0]: https://pkg.go.dev/cuelang.org/[email protected]/pkg/tool
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.
What are some alternatives?
Dagger2 - A fast dependency injector for Android and Java.
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
notty - A new kind of terminal
oursh - Your comrade through the perilous world of UNIX.
csvinfo - A small util to show max column lengths for a passed CSV file.
csvquote - Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines
awk - Random AWK code
crosh - Minimal CROss-platform SHell (WIP, code is not real yet)
w64devkit - Portable C and C++ Development Kit for x64 (and x86) Windows
ngs - Next Generation Shell (NGS)
PSCalendar - :calendar: A set of PowerShell commands for displaying calendars in the console.
scratch - Personal scratch code