Rosetta and proton are two completely different layers.

Game porting toolkit is indeed also based on wine, but that’s only the conversion of directX to ogpl or vulkan (using metalVK in Apple’s case)

Rosetta is a completely separate harware accelerated (as in, the chips have dedicated hardware for this) translation layer for x86 to ARM

Given the lengths they had to go through to get even this custom APU, I can only imaging the difficulty in procuring a first-gen ARM offering from AMD.

I swear, this is just the “VR is really here, and it’ll replace conventional gaming!” Debate all over again. I’d be surprised if it happens in the next two years. After that? Maybe, if x86 doesn’t catch up more than it already has (which I fully expect it to do).

That’s fair. I do mostly play AAA games on my deck, so “yet another android gaming handheld” isn’t at all appealing to me though.

Apple’s M-chips have dedicated hardware to accelerate rosetta 2 (support for x86 memory ordering), please stop using rosetta2 as a show of what x86 on ARM can do, as it is a vertically integrated piece of software that is not indicative of the current market for anyone outside of apple.

Just take a look at windows on those new qualcomn chips - when they do the translation, the performance is underwhelming to say the least.

Yes, it will improve, but it currently does not exist outside of Apple.

And perform terribly because it’d have to emulate x86 because there’s no native ARM games (for Windows).

There’s no way there’ll be an ARM steam deck, unless valve wants to build an android gaming handheld for some reason.

Here’s some hints:

Another word for athletic is “Fit”

Reducing the size of installers is done by “Repacking” its contents.

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

Because my pc uses 4-5 times the power to run the same ps4-era game. (Especially nice when it’s hot in summer)

So I play it on my ps5, which offers me quick resume as well.

I love pc gaming, been building pc’s for over a decade at this point, but I do also see the advantages my ps5 has over my pc.

Could I build a more efficient and quiet pc, attach it to my tv and use that? Probably, and it’d be quite good with steamOS on it, but it’d be finicky to get sleep/resume working on it, and it’d probably cost me more.

Wireguard (which is what tailscale is built on) doesn’t even require you to open ports on both sides.

Set up wireguard on a vps first, where it is accessible, then set it up from within your network. It’ll traverse NAT and everything, and you don’t have to open a port on your network.

Tailscale is the exact same thing, just easier because it does everything for you (key generation, routing, …). Their service replaces your vps, up to you if you think that’s acceptable or not. IMHO, wireguard is worth learning at least. I eventually (partially) switched to tailscale because I’m lazy, and all services I host have authentication anyway, with vpn just being a second layer.

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.

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.