Our great sponsors
goyek | just | |
---|---|---|
10 | 167 | |
504 | 17,053 | |
3.2% | - | |
7.9 | 9.1 | |
7 days ago | 6 days ago | |
Go | Rust | |
GNU General Public License v3.0 or later | 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.
goyek
- Goyek: Build Automation in Go
-
Reason to use other Build Tool than Make?
You can also take a look at https://github.com/goyek/goyek. Personally I use either Make or goyek. Disclaimer: I am the author of goyek
-
Is your makefile supposed to be a justfile?
I think that Make is so popular, because Go comes from C. Many C and C++ devs migrated to Go. Personally, I created goyek as an alternative.
-
Task runner like go-task/task, but in pure Go, no external DSLs
how about https://github.com/goyek/goyek
-
Build\task automation in Go
It's also what I'm using currently as direct make/makefile replacement. What I plan to use next time though is goyek: https://github.com/goyek/goyek . Concept looks really nice but I haven't tried it yet in any real case scenario.
-
goyek v2 is coming soon
https://github.com/goyek/goyek v2.0.0 is to be released in two months. Now it is the best time to provide feedback.
-
goyek v2 RC - feedback needed
In my "free time" I develop https://github.com/goyek/goyek
- goyek v1.0.0 is released
-
goyek is looking for feedback before going v1
https://github.com/goyek/goyek (initially `taskflow`) first release was more than a year ago. So far been slightly improved.
-
The first release of goyek - a library for creating build pipelines
Check out: https://github.com/goyek/goyek#make Also reusing Make targets between multiple repositories is harder (e.g. via git submodules) Here are some presentation if you are more interested: https://github.com/goyek/goyek#presentations
just
-
I stopped worrying and loved Makefiles
I don't like makefiles, but I've been enjoying justfiles: https://github.com/casey/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
What are some alternatives?
mage - a Make/rake-like dev tool using Go
Task - A task runner / simpler Make alternative written in Go
taskflow - Create build pipelines in Go [Moved to: https://github.com/goyek/goyek]
cargo-make - Rust task runner and build tool.
golang-templates/seed - Go application GitHub repository template.
cargo-xtask
weaver - Programming framework for writing and deploying cloud applications.
Taskfile - Repository for the Taskfile template.
CodeLLDB - A native debugger extension for VSCode based on LLDB
pants - The Pants Build System
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.