INingve·Jun 3, 2021Submission
Nomia: Precise, efficient resource management across all domain/resource types
2 points · Open discussionscarf-sh
nomia
Nix2021–2021
scarf-sh / nomia
nomia
A system for precise, efficient resource management across every domain and resource type.
3Distinct people
3Mentions
0Explicit recommenders
167GitHub stars
What to know before exploring
What it is
A system for precise, efficient resource management across every domain and resource type.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 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 week3 dated mentions
Observed mentions: 2021-04-21 14:09:38 UTC to 2021-06-03 06:25:26 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 19 | 2021-04-19 00:00:00 UTC | 2021-04-26 00:00:00 UTC | 1 | 1 | 0 |
| Apr 26 | 2021-04-26 00:00:00 UTC | 2021-05-03 00:00:00 UTC | 0 | 0 | 0 |
| May 3 | 2021-05-03 00:00:00 UTC | 2021-05-10 00:00:00 UTC | 0 | 0 | 0 |
| May 10 | 2021-05-10 00:00:00 UTC | 2021-05-17 00:00:00 UTC | 0 | 0 | 0 |
| May 17 | 2021-05-17 00:00:00 UTC | 2021-05-24 00:00:00 UTC | 0 | 0 | 0 |
| May 24 | 2021-05-24 00:00:00 UTC | 2021-05-31 00:00:00 UTC | 0 | 0 | 0 |
| May 31 | 2021-05-31 00:00:00 UTC | 2021-06-07 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
3 sourcesAnother way to address this concern. Nix allows you to specify what you want to do in this case. You can either:
1) Decide you want that patch to be applied to everything, resulting in recompiling the world.
2) Apply the patch for only the specific project you are working on/testing/etc. Thus only that thing is recompiled.
3) You can cheat in various ways if your project truly requires being updated by only changing the glibc and no recompilation is feasible. Some options: the way OpenGL and graphics is currently done in NixOS, nix-rewrite (https://github.com/timjrd/nixrewrite), and LD_PRELOAD. Breaking the abstraction in this way may have practical benefits, but you also lose the reproducibility and excellent bookkeeping of all the details that Nix provides.
4) specify a container/project/VM that uses your patched glibc, so only those th
Read the rest
ings are rebuilt that matter in your use-case.
The crux of the matter is that we need to be more precise in the names of things. Most of the time "glibc" refers to whatever is on your system on the same path. Nix has taken the other extreme where you can't just say "glibc", you really mean "this particular source, compiled with this particular set of flags and build script". If you want something more powerful\and between those extremes, there is some work currently on a system called Nomia that attempts to provide a far richer naming semantics, but it is still experimental. https://github.com/scarf-sh/nomia It would allow something like "glibc means anything ABI compatible with this particular thing, plus some other requirements...."
Nomia: A universal system for precise efficient resource management
7 points · Open discussion