

Obsidian’s only downside is that it’s closed source, but this is a big downside for some people.
Obsidian’s only downside is that it’s closed source, but this is a big downside for some people.
Yes, Joplin achieves everything this proposal does and more.
I think you accidentally dropped your mic.
That’s odd. I’ve been running OpensSUSE Tumbleweed with a Ryzen 9 5950X and RTX 3080 with no issues. I don’t know what would be making yours, with similar hardware, function differently unless it’s the laptop stuff for dynamically switching between onboard graphics and the GPU.
What kind of graphics hardware does your laptop have?
Debian and Mandrake in the late 1990s. And I was already almost three times as old as you were when you started. These days I’m happy with OpenSUSE Tumbleweed for daily use. I tried NixOS but it threatened to break my old brain.
OpenSUSE Tumbleweed because it’s very up to date yet reliable, package management doesn’t require me to get my head around anything complicated, automatic btrfs snapshots allow me to rollback if I mess anything up, and I like KDE Plasma and the YaST utilities.
Canadians have always traveled to the USA to to a bit of sneaky bargain hunting. I wouldn’t be surprised to see this start going the other way.
For personal use? I never do anything that would qualify as “auditing” the code. I might glance at it, but mostly out of curiosity. If I’m contributing then I’ll get to know the code as much as is needed for the thing I’m contributing, but still far from a proper audit. I think the idea that the open-source community is keeping a close eye on each other’s code is a bit of a myth. No one has the time, unless someone has the money to pay for an audit.
I don’t know whether corporations audit the open-source code they use, but in my experience it would be pretty hard to convince the typical executive that this is something worth investing in, like cybersecurity in general. They’d rather wait until disaster strikes then pay more.