Muscle memory is causing all kinds of problems.
I installed Nix on WSL and then used that to get home-manager and thus my zsh and neovim configs working on Windows
That’s what saved me too but I’m still stuck with unpredictable crashes, 150GB of HDD / 8GB of RAM lost in the void and bullshit ads for copilot in the lock screen …
I strive for this kind of based level
(neo)vi(m) supports multiple platforms including Windows, so no worries :)
This meme was not made by the Emacs gang.
You should have a talk with your boss about NIST keypair :x
What’s wrong about it?
I’m not OP but NIST is a very shady institution for various reasons:
- They actively work with and for the NSA
- Leaked papers have shown that they included a backdoor for the NSA at least once ( https://en.wikipedia.org/wiki/National_Institute_of_Standards_and_Technology#Controversy_regarding_NIST_standard_SP_800-90 and https://en.wikipedia.org/wiki/Dual_EC_DRBG#Weakness:_a_potential_backdoor )
- Many cryptographers are suspicious of the NIST and their selection process, e.g. Daniel Bernstein (the guy who made ED25519) is currently suing the NIST for various infringements ( https://blog.cr.yp.to/20220805-nsa.html )
Use anything NIST related with care. Use ED25519 or if not available, RSA with large key sizes (4096+).
If I’m stuck on a windows machine, one of the first packages I try to install is git-scm.org’s BASH.
It’s not actually Linux, but it’s got a command line and enough programs to really help get work done.
WSL for me.
Why not just go full WSL?
I used WSL for a job and it worked fine. It’s kind of a weird VM that doesn’t really integrate with the host OS fully, but it works for many use cases.
Git BASH has more direct system integration and hardware access than WSL, though it’s been a couple of years since I had to look at WSL at all. Hopefully they’ve improved the integration over time.
