💾 Archived View for nnix.com › gemlog › 22.gmi captured on 2023-05-24 at 17:47:18. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-03-20)
-=-=-=-=-=-=-
I'm not actually a keyboard junkie, I don't have a pile of them around the house or anything, and I can't relate to the obsessives on r/mechanicalkeyboards who appear to be spending whole life savings on input devices. I'm picky, though, to be sure, and I do get a new pair of keyboards every five years or so, one for home and one for work, then proceed to run them into the ground.
As such, there's a cyclical research activity every five years which finds me revisiting what's on the market, and deciding what to type with for the next five years.
In this cycle, a few trends novel five years ago have become common:
My three previous generations of keyboard used Cherry MX Blues. These are a tactile clicky switch, highly reliable, cheap, and common in manufactured keyboards. As I began my search, faced with the flooded market of switch brands and types, I consulted a friend, one of the aforementioned keyboard junkies, who knows my preference for click and tactility. He steered me right on the very first recommendation: Kailh Box Jade.
The Kailh Box Jade makes the Cherry MX seem light, wobbly, quiet, and gritty. There's no way in which I prefer Cherry MX Blue switches to Kailh Box Jades. They were a clear choice.
Ortholinear boards intrigued me five years ago, but I ended up going with a traditional 60% staggered qwerty Pok3r pair due to the newness of ortholinear, and the poor keycap support.
Today, however, there are plenty of keycap vendors willing to sell high quality caps in 1U form on all rows, with all manner of legends. Ortholinear is no longer an inconvenience beyond the relearning of a layout, so it had to be put into the running for this cycle.
I purchased and built a Drop Preonic to test the layout. The lessons / results:
In the end, I decided embrace the ortholinear layout. I wasn't sold on the Preonic, though. It's really small, despite having plenty of keys, and since ortholinear enforces good typing style, it somehow felt more cramped than a staggered row keyboard, with little benefit, since my hands were no longer able to cross over (such as hitting the "t" with my right index finger on occasion).
As a second test keyboard, I built an Iris v5, a split staggered-column ortholinear. Almost immediately, I felt it was easier to type on, with almost no learning curve coming from the Preonic, on which I had become proficient, if not comfortable. The Iris has a couple fewer keys, but still plenty. This would become my keyboard.
The trackpoint is an amazing pointing device, and I wish every keyboard had one. Alas, everything with a trackpoint is an exercise in compromises of another kind, and I knew it wasn't realistic to expect an ortholinear split pcb kit with trackpoint support.
Before this keyboard replacement cycle, I was a standard mouse user, either right handed or left, didn't much matter. However, with the selection of a split nominally 5x12 ortholinear board, I found myself with a couple extra 1U keys in the thumb clusters, and couldn't help but think that they might be good for mouse buttons. As I was considering my options for a pointing device to go with the on-keyboard mouse buttons, I found the Ploopy Nano.
The Ploopy Nano is a simple high-resolution pointing device which uses a 38mm snooker ball as a trackball. It's 3D printed, required a little (simple) assembly, and needs no special drivers, as a trackpoint might. It even runs QMK, the same firmware as my chosen keyboard.
Indeed, after some testing, I can't find a better alternative. Ploopy Nano lives to the left of my split keyboard, and my right hand controls the mouseclicks with the thumb cluster. My mousing is now extremely precise, and my hands remain closer to the keys at all time, reducing travel between pointing device and keyboard home row. It isn't a trackpoint with regards to efficiency, but it is a more luxurious experience, and requires no drivers or recalibration or pcb support.
Things I do miss, but not enough to regret my choice:
Otherwise, that's all, I love this pointing device.
The first of the traditional pair is settled, and I'll build a second once I have finalized my configuration. Here's what I'll be typing on for the next five years:
My keyboard layouts and firmware files are kept up to date here, if you're curious.
This is what the setup looks like.
I stopped using the Ploopy Nano. It worked great for mousing, not so much for scrolling (no mousewheel) and I didn't want to spare the hotswap socket on my Iris for a rotary encoder I might bind to that functionality, at least not right now. I wish there were a way to elegantly encode a rotation of the nano ball into scrolling, or modify the ball to be a scrollball when a key is pressed. I believe this is technically possible, but I have, like, a job and a life and I just need scrolling to work better.
Nothing else has changed about my setup otherwise. Two Iris keyboards, maps available on GitHub, and I love them both.
