Our great sponsors
mage | just | |
---|---|---|
9 | 165 | |
3,879 | 17,053 | |
0.9% | - | |
5.0 | 9.1 | |
3 months ago | 5 days ago | |
Go | Rust | |
Apache License 2.0 | Creative Commons Zero v1.0 Universal |
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.
mage
-
climate "CLI Mate": a CLI library that autogenerates CLIs from structs / functions with support for nested subcommands, global / local flags, help generation from godocs, typo suggestions, shell completion and more
mage being a build tool and climate being a CLI library, a direct comparison probably doesn't make much sense but their parsing (https://github.com/magefile/mage/blob/master/parse/parse.go) seems very similar to what I'm doing for metadata (param names / godocs / comments etc.).
-
Is your makefile supposed to be a justfile?
mage
-
Anyone else doing compiler work in Golang?
https://github.com/magefile/mage but I haven't tried it as am not a fun of make like tools.
-
Do we have a package.json/scripts section alternative in Golang?
I prefer https://github.com/magefile/mage
-
[sema v1.0.0] First Major Version Bump
We now use mage to cross-compile release binaries as proposed by u/g00py3 in this Reddit discussion.
-
//go:generate with ENV variables?
Try github.com/magefile/mage - it's written in Go and lets you write Go to run scripts rather than writing bash inside yaml ;)
-
Mage v1.13 is released - now supports magefiles in a subdir
Mage v1.13 was released as of yesterday. This included a few small fixes, and a big new feature - subdirectory support.
-
Ugly code, improvement suggestions needed
If you need build automation, use mage.
just
- Just a Command Runner
-
Ask HN: Any tool for managing large and variable command lines?
I started using just [0] on my projects and have been very happy so far. It is very similar to make but focused on commands rather than build outputs.
Define your recipes and then you can compose them as needed.
[0] https://github.com/casey/just
-
Ask HN: What software sparks joy when using?
just - https://github.com/casey/just
-
GitHub switched to Docker Compose v2, action needed
Welp there is absolute chaos in that thread -- guess it's not an April Fools joke.
I wonder if relying on CI for anything other than provisioning machines is a mistake -- maybe we should have never moved from doing things from local scripts written in $LANGUAGE.
That said, I'm probably biased since I'm a massive fan of things like `make` and more appropriately for the current age, `just`[0]
[0]: https://github.com/casey/just
-
Which command did you run 1731 days ago?
> When a command has some cognitive requirements I create a script with some ${1:-default} values and I store them all in $PATH enabled local/bin
I would consider using just for this:
https://github.com/casey/just
-
Using Make – writing less Makefile
Your coworker's experience is more principled: Make is a mediocre tool for executing commands. It wasn't ever designed for that. Although it is pretty common to see what you are mentioning in projects because it doesn't require installing a dependency.
For a repo where an easy to install (single binary) dependency is a non-issue, consider using just. [1] You get `just -l` where you can see all the command available, the ability to use different languages, and overall simpler command writing.
[1] https://github.com/casey/just
-
Show HN: Just.sh – compiler that turns Justfiles into portable shell scripts
This is fantastic, but I'd say that this solution is somewhat in response to this open issue from 2019:
https://github.com/casey/just/issues/429
I really wish just was included as a package in distributions.
-
Sharing Saturday #496
So far, I didn't work on new features at all but on stabilizing the ground for further development: 1. CMake lists and modules were rewritten a lot, now managing builds and their configurations is much lesser pain. 2. Brought in Justfile for regular tasks, and it's great, no less. 3. Linters, formatters, analyzers for almost all the code (except for Janet for now, as because of it being a niche and young technology, it didn't get enough attention yet). 4. ECS stub. Now runtime class doesn't look like a god object. 5. Started writing unit tests which didn't happen with my personal projects before and maybe indicates how serious am I about this one :D 6. Some of previously hardcoded data has been moved to INI files. Now, if I release the game in 10 years, and in 10 more years some eccentric person decides to make a variant of it, it will be slightly simpler.
-
What’s with DevOps engineers using `make` of all things?
i've grown to like this for my personal projects. https://github.com/casey/just
-
Show HN: Jeeves – A Pythonic Alternative to GNU Make
Reminds me of `just`. Which I love.
https://github.com/casey/just
What are some alternatives?
Cockatrice - A cross-platform virtual tabletop for multiplayer card games
Task - A task runner / simpler Make alternative written in Go
goyek - Task automation Go library
cargo-make - Rust task runner and build tool.
taskflow - Create build pipelines in Go [Moved to: https://github.com/goyek/goyek]
cargo-xtask
PacketProxy - A local proxy written in Java
Taskfile - Repository for the Taskfile template.
HattrickOrganizer - Assistant for Hattrick online football manager
CodeLLDB - A native debugger extension for VSCode based on LLDB
symphony-of-empires - Symphony of the Empires is a RTS strategy game and map game.
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.