tokay
busybox-w32
tokay | busybox-w32 | |
---|---|---|
4 | 16 | |
231 | 642 | |
0.9% | - | |
8.7 | 9.2 | |
about 1 month ago | 6 days ago | |
Rust | C | |
MIT License | 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.
tokay
-
The Awk Programming Language, Second Edition
[0]: https://github.com/tokay-lang/tokay
- GitHub - tokay-lang/tokay: Tokay is a programming language designed for ad-hoc parsing, inspired by awk.
-
Hacker News top posts: May 13, 2022
Tokay Programming Language\ (21 comments)
-
Tokay Programming Language
I am very interested in this project as a "better awk" is something I have often fantasized about.
I read all of the documentation that's available on https://tokay.dev/tokay-docs/, but unfortunately it never really... describes itself? Many sections, including the section on "parselets" are just unwritten. "Consumable" values are mentioned but never described (there is a "stub" section that doesn't really explain what the term means).
It begins with a pretty detailed description of value "severity" but doesn't really motivate why the concept exists. (I think that it's (basically) a way to very concisely discard certain matches? When there are "more important" matches around them?)
There are no examples of how I could use Tokay to "parse" something -- there are lots of examples dotted through the docs, but none of them demonstrate working with structured file formats, and they feel a little bit contrived.
I'm not complaining here: this project is not making any false claims about its status, the docs are clearly and explicitly unfinished, it is very clear that Tokay is still under active development.
But I want to learn more about it! I came away from that with a sense that, this has the potential to be really useful to me, but without any concrete evidence to support that. I guess the next step is to download the source and start reading through the tests.
All this to say: please highlight some examples showcasing situations where Tokay shines! (Parsing CSVs containing quoted strings was making the rounds recently, right? What does that look like in Tokay?)
Oh, actually, the GitHub readme has an example that is more involved than any in the documentation: https://github.com/tokay-lang/tokay
_ : [ \t]+ # redefine whitespace to just tab and space
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?
sparklines - Text-based sparklines for the command line mimicking those of Edward Tufte.
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
butter - A tasty language for building efficient software. WIP
notty - A new kind of terminal
mech - 🦾 Main repository for the Mech programming language. Start here!
oursh - Your comrade through the perilous world of UNIX.
react-snippets - A sample of useful snippets in React
csvinfo - A small util to show max column lengths for a passed CSV file.
textimg - Command to convert from color text (ANSI or 256) to image.
csvquote - Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines
erg - A statically typed language compatible with Python
awk - Random AWK code