Gemütlich von meinem sicheren Zuhause aus verurteile ich auch immer gerne die anderen, die sich weigern, ihr Leben aufs Spiel zu setzen
Seriously, people don't understand what "cache" means, maybe they should just create a ramdisk and install the game there to understand the concept.
I believe people with lots of RAM simply enjoy the feeling of theoretically being able to run everything, but they don't actually want processes to use that RAM, because it would deny them the theoretical possibility to run everything.
I jest, of course. The problem is that as a user you don't have that much control over which process should use your RAM, and also freeing RAM is hard. Chrome gobbling up your whole memory is good when you're using Chrome, but you don't get it back when you alt+tab back to your game
I was much more into Gameboy, SNES and later PlayStation than the DOS games that were available to me. However, once I really got into PC gaming, controllers felt extremely limiting to me and nowadays I cannot even use them anymore. I prefer mouse and keyboard even for racing games and platformers
I am a big fan of Passkeys. However, I will refuse to use Passkeys until I can sync them using my own infrastructure. I hope no major site makes them mandatory until then
I'm very interested in a solution. Our current setup, where we use an external docker host for Testcontainers and Podman to build images is quite painful
Do you have a working snippet somewhere I could take a look at?
Doesn't podman use buildah under the hood?
We are using the kubernetes executor. You can add additional sidecar services for your jobs, and we're using that mechanic to run podman as a daemon. There are some gotchas I had to solve if I remember, but now it works nicely for us. Except for Testcontainers, which throws an exception when your Testcontainer is exposing ports
Yes but imo it's easier and nicer to integrate Podman into an existing build, for example with maven
We are trying to use podman as a way to run Testcontainers and build images on a kubernetes cluster using Gitlab CI. Building works, but running Testcontainers doesn't so far :(
That's a bummer. We're strictly regulated and stuff like this needs to be self hosted or we can't use it
The best summary for NMS I have read is "huge but shallow". There is so much stuff to do, but everything is so shallow that it becomes boring very fast