ProtonBadger

Same, I've done C and C++ for several decades and I've spent too much time of that hunting obscure memory issus triggered by rare race conditions. No matter how hard we try to use safe patterns we are all too human. The most experienced C++ devs I know are the first to admit this.

In Rust once it compiles much less time is spent debugging and a whole big category of bugs are gone from the production code.

And C++ aient pretty but maybe that's subjective.

Andrew S. Tanenbaum, Computer Networks, 3rd ed., p. 83.

And one less thing to waste time on for experienced users.

Yay! Something that isn’t proprietary and resembles Obsidian!

I've been using Joplin for many years, it looks like this, works on most platforms and has [optionally encrypted] cloud support.

For a while for me it took over from drawing rectangles on the desktop.

I dunno, a lot of CEO's are probably laughing all the way to the bank.

Yeah, the author normally rarely misses an opportunity to complain about KDE being too complex in his articles - and COSMIC aims to fall in that sweet spot between the extremes that are GNOME and KDE, while adding features like optional but native tiling.

The applet concept where applets live in their own process and communicate via Wayland protocols (behind a COSMIC API) is also less likely to break than GNOME plugins that are horribly injected into its bowels.

Given the toolkit, organized development and UX decisions being up-front designed with figma sketches, etc. that are reviewed before implemented, and having both paid developers and community contributors it has a lot of potential.

This is a good thing, it is much needed for Snap and Flatpak and will make sandboxed applications less confusing for those who don't grog flatseal/kde-settings/etc. and adds convenience for everyone.

Yeah Denmark is very relaxed about bodies and public nudity in general. Denmark was the world's first country (in the modern world) to legalize porn. However, consent matters and consenting to one type of exposure doesn't mean consenting to everything.

Greybeard here. I can use vi, emacs, nano, etc. and use whatever is available if it suits the job. For many years I did dev in emacs on my computers and on other systems used vi for quick edits. Currently on my own laptop I have micro as default term editor now. For Rust development - code, though I have hopes for Lapce.

They're all just tools and so are people who get tribal about things.

Well, yes use-case is key. But interestingly ext4 will never detect bitrot/errors/corruption. BTRFS will detect corrupted files because its targeted users wants to know. It makes it difficult to say what's the more reliable FS because first we'd have to define "reliable" and the perception of it and who/what do we blame when the FS tells us there's a corrupted file detected?. Do we shoot the messenger?

For a few years I used a distro that had btrfs as default, including scheduled automatic maintenance. Never had to bother about manual balancing or fiddeling with the FS.