His videos are gold! I'm really impressed

Recently I've found Cromite and sure glad I did! Finally I've found my Kiwi browser replacement. It is also feels faster than both Firefox and Brave on Android (though YMMV).

Many people use PyO3 for that

I vaguely remember that there is a new language that promises "Safety across FFI boundary", but can't recall the name

I'm just starting my second attempt at using NixOS last week because suddenly, my SSD failed and I have limited amount of time to configure my second laptop to get to work. This time I don't think that installing Arch will be the best choice to get to the last state of my laptop as fast as possible (I'm using dotfiles management, but not all things can be automated). And I'm ready to try NixOS again.

The only thing that makes me confident this time, is that I can use LLM to help me. There is absolutely no way I could try Nix again without using LLM. The first attempt at using it just makes me anxious because of docs alone.

And what makes me stick using it? Nix-ld. I think embracing impureness and doing things incrementally will help alleviate the vertical learning curve that is Nix.

After all of this learning curve? I finally can see the rainbow that I can only dreamed of in the past.

Awesome! Thanks for making this!

from Niko's post:

> In the past, we were blocked for technical reasons from expanding implied bounds and supporting perfect derive, but I believe we have resolved those issues. So now we have to think a bit about semver and decide how much explicit we want to be.

iroh's stuff is great but their local peer discovery can't work in a browser, since it uses an mdns-like protocol to do it

I've remapped my capslock to 'tap-dance' between esc (short press) and ctrl (long press) using kanata. And, like any other people here, it's indispensable tool in my workflow right now.

Also recently, I've remapped my siblings laptop meta and rctrl key to lalt and meta respectively because the original alt key got damaged. Thanks jtroo for creating this you rocks!

Any comparison with https://github.com/jtroo/kanata ?

Based on a quick skim of Kanata's documentation, it does not appear to be context aware, e.g. have different mappings based on the application or device. This is of course a matter of preference, but I find Keymapper's configuration format more straightforward. It doesn't try to mimic QMK & friends. Rather than layers it has contexts. The concepts are similar but unlike layers, you can multiple context active at a time. Keymapper is really flexible. Pretty much your imagination and willingness to tweak stuff is the limit.