Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge. Learn more →
Just Alternatives
Similar projects and alternatives to just
-
-
-
Revelo Payroll
Free Global Payroll designed for tech teams. Building a great tech team takes more than a paycheck. Zero payroll costs, get AI-driven insights to retain best talent, and delight them with amazing local benefits. 100% free and compliant.
-
-
-
-
-
Onboard AI
Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.
-
cargo-release
Cargo subcommand `release`: everything about releasing a rust crate.
-
ripgrep
ripgrep recursively searches directories for a regex pattern while respecting your gitignore
-
starship
☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
-
-
-
AutoHotkey
AutoHotkey - macro-creation and automation-oriented scripting utility for Windows.
-
-
-
-
-
yplatform
Self-service bootstrap/build/CI/CD. Software and configuration that supports various cycles of software development.
-
-
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
just reviews and mentions
-
Makefile Tutorial
Dropping a link here for convenience: https://github.com/casey/just
I saw this further down in the thread: https://github.com/casey/just
Looks like a version of make optimized for running commands instead of builds.
-
Introduction to Immutable Linux Systems
An OCI image is pretty simple, yes, so is the sort of image that is in an OSTree repository. The difference is that when using `rpm-ostree` packages installed with `rpm-ostree install` are "layered" on top of the base image, while packages in the "base image" (be it OCI or OSTree) are part of the system and thus not "layered".
Adding packages in an image has the benefit of pseudo-reproducability (have the same image on multiple computers) and the added robustness of your base system being built elsewhere daily. Your computer just pulls the diffs. For example, there have been issues with rpmfusion on Fedora that ublue users completely avoided. Codecs & other essential rpmfusion packages are included in the images, and the rpmfusion repository is removed after they are installed. This way, if something package-related breaks it breaks at the image build stage, and an ordinary user wont even notice it before it is fixed.
The most noticeable benefit IMO, though, is being able to ship the same changes on top of a base image every day for multiple machines. This is not only packages, but for example udev rules, and other QoL things like our `justfile`s, configuration for https://just.systems/ that has some useful scripts for adding the kargs necesarry for Nvidia drivers to work and `just update` for updating the system, flatpaks & distroboxes.
-
“Make” as a Static Site Generator
My number one reason to use make is to have a single centralized location for project commands. If I see a Makefile at the root, I can quickly scan it and have an overview of what high level actions I might execute.
Note that I have recently switched to Just (https://github.com/casey/just). While not technically the exact feature set as make, it covers all of the ground for what I typically do. It gets the benefit of history and discards a lot of make cruft to make a more predictable experience.
-
Use just to manage Rust project commands
# `all` variant that only runs on Windows. The only thing that is different is the shell. # https://github.com/casey/just#enabling-and-disabling-recipes [windows] all: set windows-shell := ["powershell.exe", "-c"] just all_cross_platform # `all` variant that only runs on Linux and macOS. Using the default shell. # https://github.com/casey/just#enabling-and-disabling-recipes [unix] all: just all_cross_platform # `all` command that runs on Windows, Linux and macOS. all_cross_platform: just build just test just clippy just docs just rustfmt
-
Taskfile: A Modern Alternative to Makefile
How does this compare with `just`[0]? I've never written a Makefile but I'm a big fan of `just`.
-
Makefile Tutorial by Example
I've never learned to use Makefiles, but I've been having a good experience with the just task runner.
-
Reason to use other Build Tool than Make?
Just wait until you find out about Just :)
-
Build a desktop app with Qt and Rust
A task runner can save you time by automating repetitive development tasks. I recommend using Just. To install Just, use the following command:
-
Learn Makefiles with the Tastiest Examples
https://github.com/casey/just
`just` has some nice UX improvements over `make`. (e.g. doesn't require soft tabs, can list recipes out of the box, recipes can take command line arguments, supports .env files, can be run from any subdirectory).
-
A note from our sponsor - InfluxDB
www.influxdata.com | 2 Oct 2023
Stats
casey/just is an open source project licensed under Creative Commons Zero v1.0 Universal which is not an OSI approved license.
The primary programming language of just is Rust.