all of these various 3rd party backup tools use these things. Mostly it's QOL stuff that you get from a 3rd party tool. We use barman, very happily: https://pgbarman.org/
Barman has been around since 2011, released under the GPL. If it does get ruined by someone, I'll replace it in my stack or fork it for maintenance myself. I'm not very worried though.
EDB has been in private equity(PE) hands since 2019 with out managing to ruin it so far. The ownership in PE hands seems to be pretty stable, so it doesn't look like the typical pump/dump mess you often see from crappy PE money.
I dunno how they compare, but we have been using barman for a long time very happily. We test our backups every night, by restoring from barman into a _nightly DB. which we then give out to users as a training/testing spot, so that we know when it breaks. It hasn't broken in many years now. <3
It's typescript and pretty sure all of the Official Bitwarden clients are written in it.
I wrote a version in Python and then rust back before the official CLI was released. Now you can use https://github.com/doy/rbw instead, much better maintained (since I don't use Bitwarden anymore).
I have family I need to support, so I use 1password. It also helped that work gives me a 1P family plan free.
The practical differences to me:
* 1P is aimed at non-tech users more than Bitwarden.
* 1P lets you easily store things other than just passwords (serial #'s, license info, SSN's, etc) You can in Bitwarden, but it's a little annoying.
* 1P lets you store SSH keys(by effectively being an ssh-agent): https://developer.1password.com/docs/ssh/
All that said, I still happily recommend BW, especially for people that are cost-conscious, the free BW plan is Good Enough for most everyone.
Security wise, they are equivalent enough to not matter.
I have had many of these machines at various points in time, some even running on the public internet. They are a giant PITA to keep running and alive. This is why they don't usually last very long if they ever even get to public access(most don't).
Unless it's a super fun hobby for you, I wouldn't plan on this being very fun after the first dozen random crashes.
At work we just got a quote to upgrade a couple servers, original price a few years ago was ~ $150k. Essentially the same hardware, just newer, is now quoted at ~ $450k.
We decided to just keep our current hardware for now and extend a support contract for ~ normal price.
Quite the opposite i'd wager. Now that AI can figure everything out we can have the AIs do the performance work. Performance work alot of the times also went against developer experience in terms of languages/patterns and such. AI doesn't need to care about DevEx which might also show a shift towards more memory efficient languages and patterns. Only time will tell though.
Ya, I don't see any point in systemd adding this, but they did it already. Near as I can tell most of the laws just want to know a rough age category that can be provided by the OS. Seems to me an `echo "adult" > ~$USER/.config/law_compliance/age_category` would do the trick.
Anyone that cares can go check that file if they want an age category for some reason. Why does this need to be any more complicated?
If a parent really wanted, they could change the perms so only they could change that file.
I have no doubt that systemd will implement a place to store political party membership, religion, LGBT status, veteran or draft status, or ethnic group membership if a handful of governments start to require that information.
reply