trevor

The desktop app can be used as a bridge for biometrics in the browser extension, but other than that, it basically serves no unique purpose unless and until they add autofill for desktop applications.

Totally fair. I’m curious to see if anyone else may have reasons why it might be suboptimal.

Is the a downside to repacking the deb package? They’re basically just zip files of the same binary you’d run on most other Linux distros.

Frutiger Aero, my beloved 🤩

God damn it.

This is so true. The state of gaming on the Steam Deck is great right now. Even the foreboding unsupported status is only ever really a problem with asinine anti-cheat, and that’s just like a handful of games that aren’t worth playing in the first place.

Eww… You’re right. What a waste.

Silly question: what’s the difference between the otf and ttf fonts?

Edit: thanks for the explainers!

I know a bunch of people that own Steam Decks, know nothing about Linux, and have no idea that their games are running on it. I’d say it’s pretty easy now.

“Karen compiler” is almost perfect, except unlike Karens, the compiler is delightfully helpful with the error messages it gives you (usually). It usually gives a straightforward error, an error code, and sometimes, an easy fix.

As someone that started with Rust, but just yesterday had to fix some C++ code, working with any other compiled language makes me shudder. I have nothing but respect for devs that have to wade through stuff like that.

Just don’t ls /dev/loop* 🫣

I just pre-ordered five of these. lol. Thanks for the rec. Wendell from Level1Techs always has his eye on the coolest stuff.

I’d love some suggestions. I have a 1440p 32:9 monitor that can act as separate displays, but since Synergy, input-leap, and the other software KVMs don’t work on Wayland, I’m having a bad time :(

It’s missing trackpads, which is a pretty big oversight for a device like that.

Does anyone know of this gets us closer to having a working software KVM solution with Wayland?

I’ve tried Synergy, Input Leap, and Waynergy, but nothing seems to work, unfortunately.

This is wrong. I run Bazzite and have transfered my FF profile over without issue. The Ublue “distros” just use the FF flatpak. You can follow the same instructions as you would on any other distro to move your FF profile with the flatpak version.

I agree with your sentiment. Just one small thing: .c files are usually C source code, and are meant to be compiled into binaries.

It doesn’t change OP’s situation at all though.

It’s almost everything. You can play most games on Linux. You can’t bolt-on the quality of life features that Valve has on Windows.

There’s a reason most Steam Deck users don’t install Windows on it, even though you can.

Using containers on Linux has basically no performance loss compared to running on the host. They share a kernel and nothing needs to be virtualized (unlike containers on macOS and Windows), so anything you run in a container is basically the same performance as running it on the host.

I still agree though: using Nix is better than using Distrobox for many other reasons.

Nix has more packages , by far. Nix also automatically handles the dependent libraries for each package, which is something you can’t do with brew on immutable systems. This means that Nix can install software like espanso, which wouldn’t work on uBlue derivatives otherwise.

I really wish the uBlue maintainers would have opted for Nix over brew for that reason. It’s not much more difficult to do nix profile install nixpkgs#package-name over brew install package-name. They could have even aliased it to make it easier.