I am using a HHKB Pro Hybrid as a daily driver at work and a Realforce 104-u at home.
There is no such thing as the perfect keyboard, but HHKB Pro layout is something that stood its test of time (~10 years). And I don't see it getting replaced.
The Realforce may get benched, because I'm getting more used to wireless keyboards. So far it hasn't happened yet.
yeah, not even on the alternative downloads page. It reminds me of the story of how the Mono team had an issue in the downloads page that leads to some users download a 2yr old release of the Mono Framework.[0]
I found the downloads page[1] but it still says Beta, unsure what's going on.
This is frustrating. After realizing I can only afford a small condo in Metro Vancouver area, I moved to a low COL city (relatively) 3 years ago. While the prices are still somewhat affordable from the West Coast standard, prices have gone up significantly in the past year alone.
That setting is misleading. It just toggles whether DNS resolution happens on client side (the machine the browser is running on) or on SOCKS server side. As the SSH client acts as SOCKS server and as the SSH client usually runs on the same machine as the browser, this setting doesn't make any difference when using SSH as SOCKS proxy!
When using SOCKS over SSH and running the SSH client on your local machine, DNS resolution will always happen on you local machine as well (except when using DoH of course)!
It might seem misleading if you're using ssh as a SOCKS proxy, but there are many other SOCKS proxies for which the setting makes sense. For example, if you're using tor as a SOCKS proxy, then that setting is the only way to have the browser resolve .onion addresses.
Run containerd and buildkit in a vagrant VM. You'll have a lot more control--you can pick what kernel you want (and even upgrade it as necessary), you can expose host filesystems and devices to the VM, etc. It's the same thing Docker Desktop is doing behind the scenes but now you control the full stack.