Guix :) It's a shame its package coverage is nowhere near NixPkgs, because it's so much nicer to read and write. I guess eventually we'll have "Compile-to-Nix" languages, seemingly these sort of languages tend to crop up after a while for languages with lets say "harder UX".
Maybe it would be a good idea to translate Nix packages to Guix automatically via LLMs. Then we could close the gap in available software relatively quickly.
Unfortunately guix currently has banned LLM contributions. Its not set in stone but the developers intent to maintain a human based hacker environment. Nothing wrong with carving out ones own subculture of course!
There may be a sizable enough community interested in employing LLM usage to get together and create a dedicated channel for packages developed with them, or make a soft fork.
That being said, having worked on guix packages. Automated conversation is not so simple. The bottleneck for me is compilation time and cost. even with superdooper intelligence, you have to trial and error builds, fix mysterious test race conditions and match versions.
A powerful $5000 build server plus another several thousand per year for
The electricity cost would go a long way to speeding up this process.
Old second hand computers are not viable because the electricity cost for constantly building software on them is not cost effective.
It makes me kinda buthurt when some racist rich people can raise millions for some crappy arch skin distro soft fork, but serious, novel, from the ground up projects have to scratch around in the dirt for pennies.
The project may not have truly demonstrated it's worth to justify replacing nix, but I feel it's unique and special enough that it is deserving of some money falling from the sky. It's 1 of only 2 of this style of functional packaging distribution.
Guix being ideologically opposed to supporting macOS is what keeps me using Nix on my daily driver box. My NixOS box is there to run Steam, which I suspect is something Guix would also regard as anathema.
Yes. It is a shame they didn't use an established programming language and instead developed their own esoteric one—the same kind of issues as CMake, for example. I still don't understand why I should use a custom, crappy language to build C++ projects cross-platform. And the tragic part is that nothing else offers better functionality.
Admittedly I haven't been in the C++ space for about a decade, but back in the day I used to love premake for this exact reason. You wrote your build config in a completely standard real scripting language: lua.
I know about Premake, and I completely agree that the Lua it uses is a far more pleasant language than CMake. Still, unfortunately, AFAIK, the build system itself isn't as feature-complete as CMake, and it doesn't have as extensive support in programming editors or across the broader C++ ecosystem.
The only thing that's really wrong with the nix language is that it's not statically typed, which can let errors pop up far from the mistake that created them
I don't like the attribute dot syntax. On the positive side, it's very readable. and the left-to-right syntax is a very clear and strong organization technique.
That said, it has a problem with 'rootedness' as in 'what is the root of this attribute string'.
Firstly, 'with' keyword allows you to silently slice off the front end when the attribute string originates from a passed-in argument variable.
Secondly, when you arrive at foo in foo.bar, you have no concept of what the ancestor path looks like; someone is going to do an import of this file, likely store it in a named variable in the context it is needed, and then dispose it. Every time we need foo, it's being referenced from some ephemeral external context. So it's impossible to say or know "foo has 5 references" via static analysis unless we are just grepping it.
Thirdly, (related to above), when you declare services.tailscale.enable = true; you are relying on some ephemeral other location to find meaning in services-dot as declared in the current file. Metaphorically, we can't actually turn and face upstream looking up the call stack to easily see how we arrived (nor how many times we expect to arrive) at this site.
'Self' in the context of flakes is another great example of emphemeral-ness and non-discoverability...what is accessible under 'self'? It takes a PHD to describe it.
Allowing strings mixed in (foo.bar."baz".biz) and the expectation that you might be interpolating (foo.bar."${baz}".biz) is a whole nother ball of wax...
I'm literally English and I feel the need to defend the French here, they're among the most successful military powers in the world historically speaking. It's hardly fair to judge a thousand years of French military history by the outcome of one war where they didn't do well.
As far as your sense of humor goes, perhaps you can find a different niche than disrespecting the memory of the 100,000 French soldiers who died in the early weeks of WW2 precisely because none would surrender? That 90s revisionist trope to shame the French for not being neocon enough is beyond stale.
They're literally out there hacking other companies and even governments and they're getting ZERO legal fallout from it, so I don't think legality is something they care about.
Not if you run your own system prompt that does not explicitly contain the term "pi coding agent". Perhaps they string-match against some other stuff, too, but as long as you paraphrase the system prompt a bit, you should be fine.
I use my Anthropic subscription with Pi. I thought they would start charging me API usage at some point, but it never happened. (If it did happen, I would switch to open weights models.)