.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 😎

I’ve been to the US exactly once in my life, and I clogged the toilet at the hotel I stayed at. Never had it at home.

Probably just coincidence, but hey

it’s still comically bad compared to various alternatives, even apples-to-apples alternatives like C#.

I’d be interested to hear why. IMO Java has the superior ecosystem, runtime(s!), and community. The best part is that you don’t even HAVE to use java to access all this - you can just use kotlin, groovy, scala,… instead.

In terms of the language itself, while it (still) lacks some more modern language features, it has improved massively in that area as well, and they’re improving at a significant rate still. It also suffers from similar issues as PHP, where it has some old APIs that they don’t want to get rid of (yet?), but overall it’s a solid language.

And the people hating on it somehow never used any version above 8, which is 10 years old and EOL.

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.

Which is why we have HTML5, CSS3, and JavaScript, supported by all major browsers.

Unless you’re doing something outrageously non-standard, there is no reason to block specific browsers.

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.