Lemzlez

You really can’t use the bible against christians, unfortunately. With the millions of translations it went through, it is damn near illegible.

This passage is probably one of the worst, too.

They will just respond with “tHaTS NOt wHaT iT MeANs”, and you can’t really argue with that because it’s so poorly written.

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

I’ve had firefox as default for a while now

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.

And that's only 1 global pandemic!

The difference being that when you’re 10 billion into a renewables project, you usually have SOME generation already, whereas your nuclear reactor isn’t doing shit until it’s fully completed.

I don’t mind nuclear, but the fact is that the reactors take decades to build, whereas renewables can be deployed far quicker. Going all-in on nuclear, and then twiddling your thumbs for 10-15 years while the reactors are built doesn’t sound like a great idea.

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.

I like them as well, they work well and are easy to set up with the built-in integration.

The only drawback I find is the need to use their cloud, and the low polling rate (5min I believe).

Not dealbreakers for me, but some things to be aware of.