Dimensions itself do not carry any meaning, what matters are the neighbors to maintain a sense of similarity. Think if it like a very complex point cloud. Applying an n-dimensional rotation leads to the same point cloud content wise.
As for the number of dimensions, in a sense they are a training variable just as the content itself. The more dimensions you utilize for your embeddings the more complex your relations can be during clustering. Too many dimensions can easily lead to over fitting however and too little dimensions can usually not accurately represent the training corpus.
It does break youtrack quite severely and it took me forever to single out this extension. Afaict there's also no way to filter URLs so I had to get rid of it on my work browser :/
> I'm looking for a QMK wireless keyboard, but they're thin on the ground
The issue with wireless keyboards and QMK is that Bluetooth is such a messed up protocol and to implement it QMK would realistically have to deal with proprietary binary blobs which they choose not to. I heard there's some work on "custom" 2.4GHz transmission modes but that's not as universal or ubiquitous as Bluetooth is.
Maybe check out ZMK, basically a QMK for wireless keyboards but more opiniated.
I'm about to build a wireless corne with it after years on a wired QMK Planck.
Battery life for closed source keyboards made by big companies will always be better because they have the resources to perfectly engineer the hardware and code for every model and the willingness to cut lots of corners in terms of customizability.
Same with any other piece of hardware.
I'd personally prefer some form of wireless which is specifically not Bluetooth. For one, I'm typing this on an old desktop that doesn't have BT of any kind and I don't want to have a dedicated keyboard for choosing my OS (I sometimes use windows on this computer).
Also, sometimes there's noticeable lag when typing on a BT keyboard (I have experience with an older Apple keyboard on an MBP and with a Keychron). I've never had such issues with either of my MS sculpt keyboard or Logitech mice and keyboards (nor with my Logitech lightspeed mice which are amazing, but I realize that's something else).
Nix + home-manager is how I started on arch. After moving about 80% of my Pacman-installed packages over to nix-configured packages bit by bit over weeks and after that all of my dotfiles I plunged into nixos. Transition was super smooth, can only recommend!
You can, if your repository of choice provides a Nix channel[1]. However, the community effort is currently concentrated in the official Nixpkgs repository. So while there are numerous projects based on Nix run outside of the NixOS organization, there aren't any "major" unofficial package repository that I'm aware of. For packaging work, people just tend to contribute directly to the official repository. In fact, the volume of PRs in the official repository is so high I'm surprised at how they manage to keep going in spite of that.
It's also worth noting that many of the benefits of Nix are directly driven from being able to write custom Nix expressions. So if you want to reap all of its benefits, it's definitely worth learning. The core language is small and the experience is not so far off from writing JSON, so that part is relatively easy to pick up. The actual work lies in learning how packaging is done in Nixpkgs. This is best done by grepping around the Nixpkgs repository for examples. Nixpkgs' policy of having all packages in a single repository really shines here.
I tried using NixOS a few years ago but found it too esoteric. Learning the Nix DSL and the NixOS way of doing things might be rewarding but it has a significant threshold that I'd need to cross before I'm comfortable using it.
One of the things I really appreciate about Arch is the flexibility it offers. I'm not forced to use GRUB if I don't want to, unlike Fedora and Debian. I'm also not forced to see dm-crypt UUIDs on mounted disks like Dracut does. I can choose what I want. This latter issue was present in NixOS as well the last time I tried it.
Oh, I'm also not a fan of how unbearably slow the nix package manager is compared to pacman.
I do recognize the advantages of declarative configuration of your entire operating system though.
> Oh, I'm also not a fan of how unbearably slow the nix package manager is compared to pacman.
Building a declared environment takes quite a while and switching a NixOS or home-manager generation takes even longer. It was my main complaint about NixOS when I was starting out.
The thing I realised though is that the main scenario where you actually need the speed is when you want to try things out and for that, Nix' ad-hoc environments are much better suited.
When I want to try a new program (btop for example), I simply run `nix-shell -p btop` rather than adding it to my declared environment and sitting through a `nixos-rebuild test`.
That's usually faster and, more importantly, cleaner than installing the package to a global environment with a regular package manager.
There's also qmk's swap hands feature [1]. Qmk doesn't run on any hardware but if it does the possibilities are pretty much endless. Glad you made it through though and don't need it any more :)
It’s cool to see this in software now! My little hack was useful enough for me but I didn’t bother taking it any further because I didn’t want to fuss with patents.
Disclaimer: I am a relatively active contributor