I have been self hosting my repositories on my own VPS using nothing but Git itself (you don't need to install anything else). Sharing write access is a bit of a pain, but I tend to work on things alone anyway.
I don't see any other way? When you sleep (suspend to RAM), everything is stored in RAM and is encrypted but the master key is present in kernel memory (if I recall correctly).
However, if you hibernate (suspend to disk) the entire contents of RAM (including the master key) is written/encrypted to disk and the RAM is cleared.
When you wake the machine up you have to re-enter the passphrase to decrypt the master key to re-load disk contents back to memory.
I've tried AI tooling in the past and it felt wrong to me. The software was alright (it worked).
I don't know if anyone can relate, but it didn't feel like it was "mine". I didn't even keep the project/code. It was a working software emulator for a video game console but I felt zero connection with it and couldn't even get myself to keep the code.
Maybe I'm old fashioned and/or stubborn, but I like to write code. I like to know the minute details with regards to how things work. I like to know every function an API provides. I like to understand the differences between platforms, devices, hardware, etc. I've always loved it and always will.
I don't really get stuck, but when I do the answer is usually in documentation or a man page. I probably read documentation and man pages more than the average developer.
You could argue that is slower than asking an LLM, but I am willing to do things a little slower if it means building up my knowledge and getting stuck less in the future.
Getting a user to do _anything_ on your site is difficult.
I run a SaaS product that has closed sign ups. I get inbound email asking (sometimes begging) for access to the service. I follow up with their usecase (make sure they are a good fit, I get a lot of abuse). They respond with a seemingly good fit. I generate the account and give them access and they never log in. This happens way more often than I would like.
It's so bad, I started to wonder if there's some kind of underground market for selling accounts. In the end, people are finicky and you can't predict anything they will do.
Most dependencies in the C/C++ world come with fewer dependencies of their own (at least, an order of magnitude fewer than the average rust dependency).
Perhaps a Makefile could be considered arbitrary code execution, but we've been running Makefiles for 50 years and we haven't had the supply chain issues we see in NPM, etc.
Supply chain risk was always considered in the C/C++ world... think back to Ken Thompson's 1984 paper "Reflections on Trusting Trust" where he questioned if you could even trust your compiler.
Perhaps the main difference between the Rust and C/C++ world is less about the tooling or languages, but more cultural? I don't know, just something to think about.
Rust's standard library is incredibly thin (intentionally so). As a result, you need to use the crate ecosystem. This comes with some downsides.
1. Each crate you depend on generally comes with dozens of its own dependencies.
2. A large number of crates have few downloads. You can use blessed.rs to try an find "trusted" dependencies.
3. Cargo comes with "build.rs" for compile time code execution. Basically, your code (or your dependencies) can run arbitrary code when it first gets compiled.
4. A Github account is required to publish crates to crates.io (this sucks if you don't want to be locked in to another Microsoft system).
These are just a few of the issues I have had with Rust before switching off it.
edit:
Point #4 is personal for me. I have multiple crates published on crates.io and I cannot log in and manage them because I deleted my GitHub account a long time ago. I wonder if someone could create a GitHub account using my name and claim ownership of them...
I read this blog post and the authors other blog posts. They give off a strange vibe to me.
It's almost like a reverse doomer-doomer-ism. I'm terribly sad because others don't see the value in this thing I grew to value. It is very New York hipster.