I mainly use it for git, basic files stuff and Scripting away chore tasks, so I never experienced any limits. But maybe I just touched some of that turf now.

Huh, I had iterm running half a year ago and couldn’t see any advantage and removed it because of “simple systems” purist reasons. Guess I’ll try again.

There was in fact a process still running. Killed it, reinstalled tmux and everythings back to default. Thanks!

The file isn’t there.

I’ll double check later or tomorrow, but afaik I deleted all files that contain tmux.

It’s not about switching, it’s about hosting our services on different platforms at the same time.

It’s perfectly fine for some private page etc. but when you make business software for customers that require 99,9% uptime with severe contractual penalties it’s probably too wonky.

We got our own platform based on kubernetes and cncf stuff and we don’t have to care anymore about the metal underneath. AWS? OTC? Azure? Thats just a target parameter, platform does the rest. It’s great.

When you handle all your errs the same way, I’d say you’re doing something wrong. You can build some pretty strong err trace wrapping errs. I also think it’s more readable than the average try catch block.

I’ve found the du command (but with other flags) and it led me to some old snapshots that took up a good chunk of space. du -sch revealed some 5gb of junk in my download folder, so that was a good call too ;D

zypper clean did not too much, but I got ~40gb of space back, so thats nice. I’ll probably try to replace some of the not so close to the system stuff with flatpaks. Thats a thing I wanted to dive deeper into anyways.

For podman, I only just installed it because I wanted to learn more about container / docker stuff (it’s part of my daily professional life, but I always feel like I don’t actually know anything about it), so theres nothing to be removed. It was just the package that made me aware of the little space I had left on my disk.

Thanks, you’ve been a great help :)