IIRC MySql inherits that behaviour when running on windows (or at least older versions do)

That was a real fun time when switching OS

.eu and your local tld are often quite a bit cheaper too!

Pretty much - I’m too stupid to write my own mouse drivers for the mouse I use so all the buttons work 😎

How? The sublinks devs started the project just because they didn’t want to work on Lemmy for whatever reason. If they did, they would have worked on Lemmy. It’s either Lemmy AND Sublinks, or Just Lemmy with the same developers.

Having multiple implementations is a good thing, regardless of what language they use. They all implement the same protocol, should be (mostly) compatible, and can learn from (and compete with) each other.

Look at other OSS. There’s so many Linux distributions, Why doesn’t everyone just work on a single one?

Because everyone has a slightly different view on things. This makes the OSS community stronger.

Even if that were true - does it matter?

Java is a perfectly valid choice for something like this.

Yes, Rust is “faster”, uses less memory, etc…

Java is fast enough, though. It offers a fantastic ecosystem and, seeing as these projects are ran by volunteers who do this in their free time, there’s a lot more people willing to chip in some work.

I’m confused - does it explicitly ask you now?

I’ve had firefox as default for a while now

Kubernetes yes, but minikube is kinda meh as a way to install it outside of development environments.

There’s so many better manageable ways like RKE/Rancher (which gives you the possibility to go k3s),Kubespray or even kubeadm.

All of those will result in a cluster that’s more suitable for running actual workloads.

I don’t think programming language is a good metric for security. I assume everything I host has issues, and then try to mitigate from there.

IMHO, a better approach is to vet the project beforehand, looking at whether it is still actively maintained. I usually use things like commits, issues, etc to try and gauge whether a piece of software is actively maintained so that when an issue arises, it can be fixed.

You can mitigate much of the risk by using some basic best practices, like isolating all apps from each other (using docker, for example), using a reverse proxy, tools like fail2ban or a web application firewall, using proper database permissions for each app, etc

What I also do is add another layer by making certain applications accessible only over vpn. That won’t work for some tools, obviously, but also reduces the risk for tools you are only using yourself.

I’ve set up several Kubernetes clusters in a professional setting (and work with it daily), but I still use straight docker for running my own stuff.

Using tools like Rancher it’s pretty much no effort to set it up, but the overhead is just not worth it if you’re not using the orchestration IMO.