HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jdx
mise
Rust2023–2026
jdx / mise

mise

dev tools, env vars, task runner

40Distinct people
49Mentions
1Explicit recommenders
36.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

dev tools, env vars, task runner

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

> I went looking for an issue to see if they're planning it, but the Mise repo doesn't have issues enabled? And no discussion on the README about why they don't. That doesn't…

rsyring used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year49 dated mentions

Observed mentions: 2023-01-27 08:49:44 UTC to 2026-09-11 20:42:36 UTC.

0510152023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 4 submissions, 7 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 17 mentions; 1 submissions, 16 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 15 mentions; 6 submissions, 9 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1147
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC17116
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC1569
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC606

What Hacker News says

49 sources
> Are the changes Omarchy specific or distro-agnostic? You say both. The changes are specifically for Omarchy. They just happen to still be distro-agnostic. There is no guarantee this continues in the future. The discussions: Using managed tool-stub bundles for Omarchy’s lazy CLI layer: https://github.com/jdx/mise/discussions/12597 Proposal: give every Omarchy user a declarative "my machine" file with mise bootstrap: https://github.com/jdx/mise/discussions/12709 Proposal: give Omarchy dotfiles automatic history, easy restore, and optional sync with mise: https://github.com/jdx/mise/discussions/13022 > I don't even know what hyperland and quickshell are. I don't use mise because it seems to solve problems I solve with containers. Okay? Your lack of awareness of the tools does not change the fact that 15 millions dollars that is supposed to
Read the rest
"support the linux desktop", but right now is mostly funding its own distro.
In Omarchy Is a Power Grab
This is an interesting motivation for the project... I kind of get it, but, have you looked at fnox[0][1]? Curious how you'd compare/contrast goals with that if so, I think I prefer that as its not coupled to a single encryption tool (age) but supports age as well as multiple cloud or local options behind one unified interface... I think it can even mix multiple stores together? but I may be missing something/didn't read thoroughly yet...maybe there's a reason fnox doesn't work as well with Nix? fnox was discussed here previously[2] [0]https://github.com/jdx/mise/discussions/6779 [1]https://github.com/jdx/fnox [2]https://news.ycombinator.com/item?id=45722931
In Show HN: Secs-man, a secrets manager you can (not) rely on
https://github.com/atuinsh/atuin for fuzzy shell history (ctrl+r) https://github.com/sharkdp/bat (nice coloured cat replacement) https://github.com/abiosoft/colima (so I don't need docker desktop) https://github.com/duckdb/duckdb (performant database that lets you directly query JSON, parquet, csv files with SQL queries and convert one to the other. https://github.com/eradman/entr (rerun commands automatically when provided files change) (useful for rerunning test commands automatically once you save the file you're editing. https://github.com/martinvonz/jj and https://github.com/idursun/jjui (Jujutsu VCS, been using it for three months and I really enjoy it) https://github.com/jesseduffield/lazydocker (managing containers, images, volumes easily) https://github.com/jesseduffield/lazygit (best tui for git and outside niche git commands, t
Read the rest
he fastest way to use git.) https://github.com/jdx/mise (fast asdf, direnv, and task runner replacement) (install pretty much version of tool, language, env vars in a per directory level. (Or global if you want)) https://github.com/ajeetdsouza/zoxide (intelligent cd to move between directories incredibly quickly)
In Ask HN: What dev tools do you rely on that nobody talks about?
The beauty of mise is that as long as someone is hosting a precompiled binary for you, it's easy to get it. I just repro'd and yeah, `mise use php` fails for me on my machine because I don't have any dev headers. But looks like there's an easy workaround using the `ubi` downloader: https://github.com/jdx/mise/discussions/4720#discussioncomme... or see the first comment on this thread to see a way to explicitly specify where to find the binaries for each platform: https://github.com/jdx/mise/discussions/4720#discussioncomme... Having these kind of "eject" options is one of the reasons I really appreciate Mise. Not sure this would work for you but I'd rather be able to do this than have to manage/support everyone on my dev team installing and maintaining Nix.
In Reproducible C++ builds by logging Git hashes
I almost feel like we're looking at different things. From secretspec[0]: [project] name = "web-api" revision = "2.1.0" extends = ["../shared/base", "../shared/auth"] [profiles.default] # Inherits DATABASE_URL, LOG_LEVEL from base # Inherits JWT_SECRET, SESSION_SECRET from auth # Service-specific additions: STRIPE_API_KEY = { description = "Stripe payment API", required = true } REDIS_URL = { description = "Redis cache connection", required = true } PORT = { description = "Server port", required = false, default = "3000" } From fnox[1]: [secrets.DATABASE_URL] provider = "onepass" value = "Database" # ← Item name in 1Password (fetches 'password' field) [secrets.DB_USERNAME] provider = "onepass" value = "Database/username" # ← Specific field [secrets.API_KEY] provider = "onepass" value = "
Read the rest
op://Development/API Keys/credential" # ← Is the similarity that they both refer to providers (as did Terraform and countless other config tools before it)? Or profiles (like aws-cli and countless other config tools before it)? Because other than that, I'm not really seeing it. And if I hadn't seen either of these, and my boss ordered me to implement something like them, I almost guarantee I'd use similar names for things because those are the common terms for them in industry. Honestly, I'm not invested in either of these. They both look nifty, but I couldn't personally care less if either (or both or neither) of these catch on and become standards. I'm only commenting here because your statement here and on the linked discussion[2] ("it's almost a verbatim copy") seems incredibly aggressive, and to me, quite offputting. They don't look alike at all to me, other than that they both aim to do similar things and thus will have some natural overlap in terminology. [0]https://secretspec.dev/concepts/declarative/ [1]https://github.com/jdx/fnox [2]https://github.com/jdx/mise/discussions/6779#discussioncomme...
In Fnox, a secret manager that pairs well with mise
rsyring·Oct 6, 2025Recommendation phrase
> I went looking for an issue to see if they're planning it, but the Mise repo doesn't have issues enabled? And no discussion on the README about why they don't. That doesn't inspire confidence. I'm not sure when/why the issues were turned off. That's...surprising. There used to be an issue that said the maintainers preferred discussions over issues. I'd link to it but it's a 404 now. I've started a discussion regarding the lack of issues: https://github.com/jdx/mise/discussions/6566 Regarding confidence: I've used the project for a couple years now. I have a ton of confidence in it and I recommend it to everyone. While preferring discussions to issues is uncommon, the release frequency and utility of mise speak for itself. Take the time to look around the discussions and/or just use it. :)
In Mise: Monorepo Tasks

Showing the 15 most recent of 49 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.