As a counterpoint, I installed Bazzite on a Blade 14 for a heavy gaming friend who was leaving Windows, and they have had no issues whatsoever.
I personally use Bluefun, and again, no issues at all. Incredibly good experiences on both.
I can't imagine what you mean by needing more work to configure, they both worked out of the box with no configuration.
You can't know with certainty on Signal that the client and the server are actually keeping your messages encrypted at rest, you have to trust them.
With Matrix, if you self host, you are the one in control.
It's harder to create new content than to correct existing content.
Just remember that Cloudflare decrypts and re-encrypts all your data, so they can read absolutely everything that passes through those tunnels.
money corrupts
This is exactly the reason that Proton became a non-profit:
https://proton.me/blog/proton-non-profit-foundation
Swiss foundations and their board of trustees are legally obligated to act in accordance with the purpose for which they were established, which, in this case, is to defend Proton’s original mission. As the largest voting shareholder of Proton, no change of control can occur without the consent of the foundation, allowing it to block hostile takeovers of Proton, thereby ensuring permanent adherence to the mission.
They're not really comparable since Bitwarden has the source available for auditing and Proton Pass (server) does not.
I'm not aware of any other enterprise password management where the server source is available and auditable. Proton certainly is not.
What features will depend on the close-source part, and which do not?
There are definitely some terminology issues here.
The SDK is not closed source, you can find the source here: https://github.com/bitwarden/sdk
It might not be GPL open-source, but it is not closed either.
Other than that, I agree with your points. I don't agree with the kneejerk hysteria from many of the comments - it's one of the worst things about FOSS is how quick people are to anger (I am not referring to you here).
But all of that still doesn’t explain what their goal of introducing the proprietary SDK is.
Let's wait and see before we get out the pitchforks.
Sorry that's my mistake - I should have said "source available", rather than "open source". IMO, being source available is the critical component of a password manager like Bitwarden, and is what I meant when I referred to their main competitive advantage.
They might also choose to be open source and fix this specific issue and return to GPL-compatibility, but remaining source available would seem to be the more critical factor.
Well, then it would be nice to hear from them an explanation on why they decided to violate the GPLv3
Lucky for you, they provided that explanation:
That may or may not be the case, but the comment I replied to said they locked the thread with "no explanation".
The draw is that you cannot screw them up. Non-power users are the ones who will get the most out of them!
I know that I'll never get a call from my friend saying, "I ran this command I found on an Ubuntu forum, and now my system won't boot..."