It runs in the kernel of the OS as a driver, which means that it’s basically a trusted malware that has even higher permission than the admin of the computer, and have access to more things than yourself, to closely monitor the whole system in order to find signs of cheating.
I think there’s no need to stick on 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.
Well, yes. I was trying to say that their rewrite still “works” at each commit being a hybrid of Rust and C++.
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 way easier than pwsh.
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.
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.
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
Guile and Guix is way better documented than Nix. The language have more features, so you don’t have to use a hack to load packages, can actually know what is accepted in a function instead of blindly copying what others do, and it comes with a formatter.
You can swap it with the standard one. It’s on another non-official channel called nonguix.
Note that skim performs worse than fzf. There’s a new matcher in Rust called nucleo which is faster, but it currently doesn’t have a cli and can only be used inside Helix editor (hx)
nu is probably the best shell for ad-hoc data processing, handling all my daily needs in one expression.
fd and rg have another thing in common, that they’re both 50% shorter than their traditional alternatives /s
Compared to btrfs it’s claimed to be faster and having working RAID support. Its unique feature is using a fast device as cache to speed up access to slower, larger disks, I think.
Some have better ux, some support more platforms out of the box. I don’t find it a good idea trying to replace everything though.
I’ve tried Joplin, Logseq, and Obsidian. The best one was Obsidian but it’s not FOSS and is getting bloated over time.
I’m settling on zk now. This small command line utility solves almost all of the note managing needs for me.
Double links and tags make me forget about these “infinite free board” functionalities in OneNote: turns out they tend to be used inefficiently. Graphical sketches can be embedded in markdown or linked to a drawn picture.
The best thing about zk is that its notes consist of plain text and no extra tracking data is required outside of the file (unlike any others above), which means it’s absolutely free to pair it with / move on to other tools when needed, or working temporarily without the support of it.
Lol it reads like a uno reverse card against the Linux trial articles in previous years:
As far as I can tell the article comes from real Windows experience though.