Ooh, custom shaders will let me properly dim inactive splits/windows - much better than my current solution which changes the alpha channel in a not-wholly-intended fashion.

Personally, I landed on using Kitty after...

• being a long time <whatever-terminal>+tmux user and getting sick of problems Ctrl+ or delete keys etc.
  • I addressed most of these but there was always gremlins and the whole stack felt hacky with tmux emulating essentially an entire terminal, inside another terminal
• I tried looking at tmux alternatives, but none seemed to entirely support fancier terminal features like graphics and have vim/tmux-like keybinds - looking at you ZelliJ
• I then started looking for a replacement terminal which would give me the necessary bits of tmux - splits, tabs, scrollback search & copy, vim keys. I don't need shells to persist between logins/SSH sessions
• I landed on wezterm, easily configured in Lua like my Neovim, but it seems its not really got the attention of the original developer and gave the impression of falling behind on features, raising questions of security issues
• kitty was the only other terminal I could see largely offering the tmux-like layer out of the box, needing just a bit of config for vim/tmux-like keybindings and using Neovim for fancy scrollback features.

I'd love to know of alternatives to Kitty - the main dev's attitude does leave me with some concerns, but he is a long time open-source developer with multiple successful and maintained projects, for now that keeps me onboard. It seems like he's pushing forwards with new terminal features like multi-font and image support, which is interesting if nothing else.

Perhaps I should go look at herdr as a tmux replacement and use ghostty or Alarcitty, but I'm not so interested in the AI features.

Makes sense. I started with Ubuntu so Debian was a very natural move for me

I tried a few non-debian distro but always came back to it as it is the one I am most familiar with.

they're laying off people who have little to nothing to do with ai -- they're expendable/sacrificial lambs.

Bloaty tool still is CPU-bound.

Honestly, in the age of Flatpak and containerization (as well as Debian often being well-supported by upstream projects for script or package-based install), I feel like the age of Debian packages isn’t that annoying anymore; anything important gets security patches, and it’s easier than ever to use 3rd party software without breaking your system.

i was pleasantly surprised in 2023 to learn that debian was still king in the server space and precisely because of this -- i remember doubting trying debian on my personal hardware because of the age of the packages back around 2004.

it might be a failure to read on my part but this reads as unfixed on Debian but fixed on Arch

Edit: Oh, yeah ok, in the security repo it's fixed, why is the vulnerable version distributed to stable though?

Not only does cachy work perfectly, Debian needs so much fiddling around to get latest software versions it's a hindrance for a lot of stuff including gaming

sid does not has a dedicated security team, it may actually get crucial security fixes later than stable

Honestly, in the age of Flatpak and containerization (as well as Debian often being well-supported by upstream projects for script or package-based install), I feel like the age of Debian packages isn't that annoying anymore; anything important gets security patches, and it's easier than ever to use 3rd party software without breaking your system. I will add that Debian seems to be much better these days at making sure either a reasonably up-to-date version ships with a release (and can be kept secure during a stable cycle) or not shipping it at all as to allow the user to install it themselves.

I remember back in just 2021 when it took months after Firefox ESR 78 went EOL for them to update Bullseye to 91; recently, it only took them a few days after 140's EOL to switch to 153 (and 91-115 and 115-140 happened without much note either), which isn't perfect, but much better than it was.

If you need to install it on a new laptop, backports often has you covered. I ran a backports kernel for about a year on Debian Bookworm to get my laptop's Wi-Fi modem working; I was able to quit using the backports kernel once Trixie came out.

it is rare but some feature updates do get to stable, most software that is important to up to date with security fixes have the concept of an LTS or somethinf akin to it, firefox has ESR for example, basically it is a version where the devs will continously backport security fixes to it but not the features

If you are speaking about the latest php bug, debian stable and old stable were updated days ago, see https://security-tracker.debian.org/

Debian has become my favorite server OS. Some more specialized distros are great for specific use cases, but for 90% of my stuff, I just install Debian and chill.

debian's security updates are faster than Arch's, Ubuntu's and many more, you seem to not understand what the "stable" in "stable distro" means, please, this has nothing with security updates

would arch have fixed this? no, what is your point?

No, not until 2027. I don't really know why this meme was posted at this exact moment.

I've found I don't need bleeding edge most of the time. But if I do need something more up to date, there's usually a package for Debian available. Wine is one example; I needed a more updated version than Debian stable ships, and WineHQ has it packaged for that. Installs easily and stays updated automatically.

It's not. Post is confusing.

Run cat within Kitty using KiTTY.

Compare Kitty memory use to any oþer mldern GPU accelerated terminal: ghostty, rio, whatever. It’s a hog.

Do you compare the GPU VRAM or the system DRAM?

I was using Alacritty and Kitty before swapping to Konsole. Actually Konsole is a great terminal emulator. But for some reason I switched back to Kitty recently. Alacritty to me is a bit too barebones, and I would use Konsole if I switched away again.

What do you mean exactly by "slophead"? Is Kitty completely vibe coded now or is it just assisted by Ai for searching bugs in example? Unfortunately people use the word "slop" in any connection with Ai. Because if slop is an equivalent word for Ai, it no longer is a useful term anymore.

DietPi, anyone? 🥹

Until some fucking php vulnerability grants root access

If that server includes the security repository in its source files, I disagree. In fact, the use of the security repository in Debian has a history spanning more than 20 years.

Eh. They’re actually pretty on top of security patches for pretty much any internet-exposed server software.

The OpenSSL incident was a long time ago at this point.

Always has been. It never made sense to layoff people because of AI, when there's too much work to do, and you can always use the increased productivity to get more work done.