Stick to stable for production. Patches for vulnerabilities will go to stable asap. That’s where you want them, not testing or unstable.
Stick to stable for production. Patches for vulnerabilities will go to stable asap. That’s where you want them, not testing or unstable.
That’s odd… all the projects i use document their install process fairly well, most of them using either cmake or autotools.
The only “terrible” scenarios i occasionally encounter is, yes, trying to automate the android toolchain - i blame Google though, not C/C++ as the Android toolchain is intentionally designed to be used with Android Studio and trying to veer of that is increasingly harder.
Even cross-compiling for windows isn’t that bad.
I know it is unpopular to say this on the Internet,
Not really, just look at any of the Critical Drinker’s takes on the Acolyte.
´How about no automotive data?
-std=C++17
, check.
XMPP is still around although there’s a constant campaign trying to claim it’s gone.
write code that almost reads like a sentence
You mean COBOL?
The Code is my Bible.
Things I encounter include incomplete documentation, outdated documentation and written process details that have assumed knowledge which makes it difficult for junior Devs to pick up.
Yeah seems about right… off the top of my head:
I’ve been trying syncthing,
It’s what i use but on the phone i only turn it on when i want to sync, otherwise it might drain battery. Always running on the PC.
Mega also works.
two options are responsibly, or anonymously.
Screwing around with big tech i’d go with and, not or.
something end-to-end encrypted.
required SSL certs and I did not have the mood to configure them.
…right…
Did you look into snikket? It’s XMPP-in-a-box.
That’s Wireguard, no?
Should’ve been ‘bunny’.
frustrated debugging log message
Just use porn actresses’ names. Or so a friend told me…
Add (offline, regular) camera.
Ever heard of Rocky?