absolutely grotesquely bad Apple Maps they integrate
You can use !maps query to workaround that. I typically end up using DDG as a frontend to other sites through its bangs syntax.
E.g.
!maps x location to y location
But yeah, if normal DDG results don’t work for you it’s probably not a huge gain.
In fact, if you are capable of the admittedly high bar of self hosting, use bit warden instead.
Vaultwarden, typically, because it’s fully free and more resource efficient. But bitwarden as the client of course.
It looks like you’re actually using Pipewire, so you’ll want to look at the documentation / bug tracker for that instead.
At first glance, sure it would be easier to read, but if you have to look for the types then things get much harder. Either the types will be in comments, on different lines, or in a different file entirely.
This is pretty much how OCaml works and you can omit the types altogether if you don’t specify an interface file, in most cases. But it’s not hard to deal with in practice since IDEs (and text editor + LSP plugin) can easily show the inferred type on inspection.
Nevertheless, I don’t really find Rust to be ugly either.
Pandoc.
It’s working with Sway from a quick test:
swaymsg output DP-1 scale 1.7
But XWayland is blurry as expected (that’s the big blocker, or all useful apps being ported to Wayland).
If it launches via a systemd service, you can perhaps edit the file such that it depends on Pipewire before it launches.
Or disable the built in startup support and create your own service that does the same.
Yes, but not in a stable version. Although I’ll say that the daemon
is still bugged for me with pgtk, but it could be a distribution issue.
First release to have the pgtk port, which means native Wayland.
DDG results weren’t too bad, although repetitious and focused on the history of the gag, and not particular examples.