moonpiedumplings

Should be awful for gaming. It’s possible to run x86 things with emulation, sure, but performance (especially single-thread)

Most modern software (games excluded), is dynamically compiled. This means that it’s not all one “bundle” that runs, but rather a binary that calls reusable pieces of code, “libraries” from the binary itself. Wine is dynamically compiled.

What makes modern x86 to arm translators special, is that the x86 binary, like an x86 version of wine, can call upon the arm versions of the libraries it uses ­— like graphic drivers. It’s because of this that the people on r/emulationonandroid managed to play GTA 5 with 30 fps via the computer version. There definitely is overhead, but it’s not that much, and a beefy machine like this could absolutely handle it.

https://moonpiedumplings.github.io/blog/scale-22/#exhibition-hall

The Facebook/Meta table had a booth where they had an ARM macbook that was running steam and they were installing games on it.

ut I honestly doubt ARM can with the overhead of emulation

Most modern software (games excluded), is dynamically compiled. This means that it's not all one "bundle" that runs, but rather a binary that calls reusable pieces of code, "libraries" from the binary itself. Wine is dynamically compiled.

What makes modern x86 to arm translators special, is that the x86 binary, like an x86 version of wine, can call upon the arm versions of the libraries it uses ­— like graphic drivers. It's because of this that the people on r/emulationonandroid managed to play GTA 5 with 30 fps via the computer version. There definitely is overhead, but it's not that much, and a beefy machine like this could absolutely handle it.

https://moonpiedumplings.github.io/blog/scale-22/#exhibition-hall

The Facebook/Meta table had a booth where they had an ARM macbook that was running steam and they were installing games on it.

Yes:

https://moonpiedumplings.github.io/blog/scale-22/#exhibition-hall

The Facebook/Meta table had a booth where they had an ARM macbook that was running steam and they were installing games on it.

I never got uefi images booting properly on those grub multi boot utility drives. Granted the last time I bothered with it was like 10 years ago now

I haven't had any issues with Ventoy, everything I've attempted to boot works. Doesn't matter how it does it if it works.

They are not explicitly designed to boot ISO's?

Also, price. I'm not gonna pay quadruple the price for something that can be done entirely in software.

Perhaps Ubuntu already has it already, but some kind of built in tool to make deploying clustered/high availability MariaDB would be nice.

The current problem with ventoy is that proprietary blobs are essentially an unauditable possible security backdoor.

This product is entirely proprietary, including the hardware, and even worse.

It's very possible that the digital Euro will be a GNU taler system.

https://en.wikipedia.org/wiki/GNU_Taler

n 2020 the project received a grant from NLnet and the European Commission's Horizon 2020 Next

The European Commission is the Executive Arm of the EU.

The original version of synapse is written in python, which still has issues with single threadedness and the global interpreter lock.

Right, but you could have just made one yourself

And then there would be a bus factor of one. It's not just about making a helm chart for myself, it's about having something that can be shared with the community, that doesn't depend on any single person to be maintained and updated.

It's about having an organization that provides "packages" for Kubernetes, for people/orgs that don't have the time, expertise, and energy to maintain them.

I greatly respect Ananace, who is in the comments of this post, and mentioned their Helm charts. The work is excellent. But looking through the commits, it's just one person, doing something that primarily consists of bumping version numbers. Contrast this to the Matrix ESS helm chart, where the commits consist of many more contributors, and also include feature additions to the helm chart.

Hello Ananace! :)

I actually have seen your helm charts many, many times before when searching for matrix, synapse, or lemmy on Artifacthub.

An official helm chart isn't really a hard requirement to me, even if I were to use one and it were to stop getting maintained, I could continue on my own. But an official helm chart has big community benefits that are very important to me. Like, there becomes the option of paid support, which is a must have for many entities. Also, an official organization may support a wider variety of usecases than someone making helm charts for personal use.

I also ended up chatting with one of the core devs of Synapse about ways to improve regular Python Synapse for use with Kubernetes back in the ending of January, so hopefully it’ll improve in that direction when time allows

Do you know anything about the claims that they have rewritten synapse in rust?

Yes and no. There are many things that are much easier with Kubernetes, once you figure Kubernetes out.

High availability is the most notable example — yes, it's doable in docker, via something like swarm, but it's more difficult. In comparison, the ideas of clustering and working with more than one server are central to the architecture of Kubernetes.

Another thing is that long term deployments with Kubernetes can be more maintainable, since everything is just yaml files and version is just a number. If you store your config in code, then it's easier to replicate it to another server, either internally, or if you share it for other people to use (Helm is somewhat like this).