Did they fixed the kernel panic problem that persisted in the last two versions? I don’t dare to try it, last month their proprietary driver has almost destroyed my machine.

You can use Nix on Guix System and vice versa, but it’s like installing them as a package manager on a foreign system. The store and packages currently are completely isolated between the two, although there’s a very early plan for a common store interface.

No, monadic interface is used to programmatically access the store instead of being used to define packages. Packages are pure in Guix.

Guix uses Guile everywhere. Nix uses string interpolated Bash and Perl for anything impure.

Now what do you think?

Fyi, it’s now available on nixos.

Nobody has mentioned that Guix is readily available on NixOS right now? Add a line to your config and it’s ready to go. Compatible with everything else.

I think there’s no need to stick with one particular language. It benefits to learn more languages and bring the “good parts” of their design into your code whatever you are writing it in.

Btw It happens that I’ve learned a bit of RISC-V, with Rust.

I’d say no. Programming safely requires non-trivial transformation in code and a radical change in style, which afaik cannot be easily done automated.

Do you think that there’s any chance to convert from this to this? It requires understanding of the algorithm and a thorough rewrite. Automated tools can only generate the former one because it must not change C’s crooked semantics.

1. breaks compatibility
2. breaks compatibility
3. breaks compatibility
4. hard to add without breaking compatibility

Then we arrive at Rust as a natural outcome.

And it’s of course possible to migrate to Rust from C or C++ progressively, fish has almost got it done.

Yeah, I literally learnt how nix works through guix documentations.

I believe that I’m already using it on NixOS. Working without visible problems since half a year ago.

It kinda fills a niche.

I use fish for simple command pipelines as well. But traditional shells are not as good when I need to do anything “structured”, because they treats almost any value as a string and don’t have anonymous functions. The first problem means that you have to parse a string again and again to do anything useful, the second means that when both pipe and xargs fails you are doomed.
Nu solves both of the big problems that matters when you want to do rather complex but ad-hoc processing of data. And with a rather principled design, nu is very easy to learn (fish is already way better than something POSIX like bash though).

Personally another important reason is that I have a Windows machine at work and nushell is much easier than pwsh.

Btw fish is also going to be a “tool in rust” soon :)

A git server don’t need to know email to work, and it is not required to have a git server. Email in this workflow is an alternative to a PR: contributor submit a set of commits to the maintainer (or anyone interested). Then the maintainer is free to apply or merge the commits. After that the code can be pushed to any servers.

I’ve tried it and I think it’s easier than a natural language to learn. Modulo the speaking part.

Honestly I’m surprised that so many people don’t know how git can be used without those repository hosting sites. That’s one way to use it, not the only way. And it’s not even the way it was originally designed for.

Checkout git format-patch.

Git and Email are not mutually exclusive. In order to collaborate with git, you need and only need a way to send your commits to others. Commits can be formatted as plain-text files and sent through emails. That is how git has been used by its author from literally the first release of it.

Kent just made a reply on this.

TL;DR: Fast on his machine. The reason of the difference is unclear though.

deleted by creator

This reminds me of a similar experience.

The first release of WSL(2) 1.0 (this versioning alone is worth another post here, but let’s not talk about it) have its CLI --help message machine translated in some languages.
That’s already evil enough, but the real problem is that they’ve blindly fed the whole message into the translator, so every line and word is translated, including the command’s flag names.

So if you’re Chinese, Japanese or French, you will have to guess what’s the corresponding flag names in English in order to get anything working.
And as I’ve said it’s machine translated so every word is. darn. inaccurate. How am I supposed to know that “–分布” is actually “–distribution”? It’s “发行版” in Chinese and “ディストリビューション” in Japanese.

At last I had to switch my system language to English to set a WSL instance up. From then on I never use any display language other than English for Microsoft products. Sometimes “translated” is worse than raw text in its original language.

Related links if you like to see people suffer:
https://github.com/microsoft/WSL/issues/7868
https://github.com/microsoft/WSL/issues/4111

PS: for the original post, my stance is “please don’t make your software interface different for different languages”. It’s the exact opposite of the author has claimed: it breaks the already formed connection by making people’s commands different.
It’s the CLI equivalence of scrambling every button to make sure they are placed differently in different languages in GUI. I hope this sounds stupid enough so that no one will try it.
A not-so-stupid way that I can think of is to add a “translation” subcommand to the app that given any supported flags in any language it converts them to the user’s language. Which is still not so useful and is not any better than a properly translated documentation, anyway.

There is a pre built distribution, you need to configure binary cache to get it. Refer to the “Substitute for nonguix” section: https://gitlab.com/nonguix/nonguix