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.

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 :(

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.

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.

If someone could build a preconfigured image that has Phosh and basic phone apps, I would consider using this full time.

Seriously. The Luddites were mostly correct about their objections to technology being used to replace humans and making exploitation more efficient, making OP’s misuse of the terms that much funnier.

Synergy doesn’t work with Wayland, sadly.

Be warned: Synergy doesn’t work with Wayland.

This is all I want to know. If yes, I’ll pass.

While I generally agree with your skeptical attitude toward this, I think the fact that they were targeting Apple’s Metal graphics API to built the most performant possible IDE makes sense. You can’t just snap your fingers and have a Linux graphical stack start working with your software.

I think the reason they targeted macOS first is probably because many of the dev team uses Macs.

As a Linux user, I’ll happily wait for software like this to get ported to native Linux APIs so we get performant text editors instead of more Electron crap.

Thank you!

How do you get plain-text logs instead of the garbage binary format that journalctl forces on you?