Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jonringer117
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
jonringer117
1mo ago
That would require assumption of good faith from all participants. This resignation post reinforces the view that there is little good faith assumptions amongst the broader Nix ecosystem.
2.
▲
by
jonringer117
1mo ago
There was an architecture team which existed, I would assume the usage of "core" was to disambiguate. https://github.com/nixpkgs-architecture
3.
▲
by
jonringer117
1mo ago
Nix ran for many years with very little to no structure. This worked fine as long as the community has some cohesion around it being a FOSS project. But political divisiveness happened around 2021 and crept into the community. You're s
4.
▲
by
jonringer117
1mo ago
If you're unemployed enough, I have a long winded video on the 2022-2024 drama. From the perspective of the guy who was labeled a nazi and banned. https://www.youtube.com/watch?v=gp0FI8Gw1iA
5.
▲
by
jonringer117
1y ago
Hi Hexa, Since you were a moderator at the time of my ban, would care to expand as to why I was banned, and what you meant by "purge the Nazis?"
6.
▲
by
jonringer117
2y ago
(Thanks for all your work on rust) There is some work to get nix to work with Windows, this is mostly being done by john ericson. However, the real issue is that nixpkgs (the repository containing all nix expressions) heavily assume unix pa
7.
▲
by
jonringer117
2y ago
There's nothing wrong with the fundamentals of Nix. But working with nixpkgs is quite difficult for most. Which is why I'm attempting to address those issues in a fork, Ekapkgs. The repos will eventually expose optional flake entr
8.
▲
by
jonringer117
2y ago
That there's an established clique? I agree.
9.
▲
by
jonringer117
2y ago
Well, the activity around changing the status quo was done in a github issue [1]. Which sat around for many months after proposing the Apache Software Foundation's sponsorship policy of "state of nexus". Which didn't giv
10.
▲
by
jonringer117
2y ago
For those that are curious about an alternative perspective on this matter, I detailed much of my personal views in my reddit suspension post. I don't have much context on the EU NixCon 2023 events, but I've been actively involved
11.
▲
by
jonringer117
2y ago
There's a lot of issues right now around communication, moderation, and community. - One of the release managers (myself) was banned/suspended [1] - Attempts to assert control on the board's decision-making by proxy group [2]
12.
▲
by
jonringer117
2y ago
Correct, there was an open letter [1]. And to clarify above, there was no "contributors of this company" dynamic to the outrage. "jobs" are things which come and go, not a lot of people are will to burn their personal im
13.
▲
by
jonringer117
4y ago
Nice, really interesting usage of nixpkgs :). Almost a command line friendly version of docker build. I like it.
14.
▲
by
jonringer117
4y ago
Compost takes 20 days to 20 months depending on the feed stock. The main issue with compost is that it can be effective in high-intensity operations like market gardens, but it's much less effective on large acre operations (corn, soy,
15.
▲
by
jonringer117
4y ago
For external users, probably the most exciting "feature" is the use of a calamares installer for the gnome and plasma isos.
16.
▲
by
jonringer117
5y ago
This likely wouldn't work on practice. Nix is aggressively lazy, so if you just want a single package, you don't have to evaluate the builds of all 60k+ packages, just the package you wanted and its dependencies. This just might b
17.
▲
by
jonringer117
5y ago
Builds break over time[0]. Generally this is from big updates like gcc, glibc, llvm, openssl, etc. Most software which is maintained upstream and within nixpkgs is fine. But there's a bunch of "cruft" that you accumulate over
18.
▲
by
jonringer117
5y ago
Oh, nix-env.... The tool which attempted to bridge the worlds of nix and traditional package managers. But has all of the quirks of both.
19.
▲
by
jonringer117
5y ago
Copying my comment from reddit[0]: For clarity, Arch has about 10k packages, AUR has around 60k packages. I believe this post is "just" about the 10k. > I’d like to see someone do this for Ubuntu, Debian, and NixOS and watch th
20.
▲
by
jonringer117
5y ago
Impressive trolling. > deepSeq is basically useless because of how almost every datastructure is ciruclar Circular references will cause "infinite recursion", and these will cause evaluation errors. So valid nix code will not c
21.
▲
by
jonringer117
5y ago
terraform is more about reconciliation of a configuration, and moving a state closer to a desired end state. NixOS is congruent configuration management. There's a 1 to 1 correlation of configuration to reality, with no configuration d
22.
▲
by
jonringer117
5y ago
> And about Home Manager, the reason why I think it's over-hyped is because it provides a declarative approach to something that was... already declarative. Your $XDG_CONFIG directory does not need a leaky Nix abstraction on top of
23.
▲
by
jonringer117
5y ago
I generally use `nix repl` for this. I have an example of myself looking at what my configuration.nix renders to while debugging a module I was adding to nixpkgs/NixOS. https://youtu.be/bkDYmvKINm8?t=1949
24.
▲
by
jonringer117
5y ago
`nix.gc.automatic` is implemented as a systemd timer to run `nix-collect-garbage` periodically. `nix.optimise` is just a nix conf option. Meaning anytime nix creates a store path, it will automatically dedup files by hardlinking them to a `
25.
▲
by
jonringer117
5y ago
> Python has pyenv, NodeJS has nvm, Terraform has tfenv, and the list goes on. Nix makes these all largely irrelevant, in a consistent way. If anything I would say this supports nix's usage. > Then if you're running on a ser
26.
▲
by
jonringer117
5y ago
Because it's a domain-specific-language, optimized for packaging software. The relevant passage: > Its only purpose is to describe components and compositions. A component is created through the derivation primitive operation, which
27.
▲
by
jonringer117
5y ago
Currently, there's 8.7k stars, 7.2k forks. And 2000+ maintainers have added themselves: https://repology.org/repository/nix_unstable So, I would say a pretty large portion. Also, the contribution model for nixpkgs
28.
▲
by
jonringer117
5y ago
> - You can't print anything because the language is lazy. Forcing any values to print them can and will result in random operations happening on your store. You can never know which values are safe to inspect. This kills debugging.
29.
▲
by
jonringer117
5y ago
> It's not a hashmap, or a map, or an object. No. It's an attrset. Riiiiight. This was intentional. Most hashing algorithms don't guarantee a stable ordering of keys. Nix was inspired by a research project called Aterm, wh
30.
▲
by
jonringer117
5y ago
All builtins functions can how render doc with `:doc` in the `nix repl`. I think there's work to make this possible with any arbitrary function.
More ›