While we personally don’t normally go for straight-up ortholinear keyboards, this one looks split enough to be comfortable. We love that there is both an ISO Enter and a regular-sized Return, although we might put another Enter on the left side if it were our keyboard. That’s the beauty of this whole open-source keyboard thing, though. I could assign any number of those animal-capped keys to Enter. Another plus is that The Railroad uses semi-normal keycap sets, with none of this 1.25u nonsense of certain split keyboards.
All the files and the BOM are available on GitHub under a Creative Commons license. This represents JLCPCB’s max length, by the way. [DiplomacyPunIn10Did] wanted to add a num pad, but it would have made it too long. Since the pictures are so big, we put our hands up to the screen to test it out. Those innermost 1u thumb keys look like they’re placed just far enough in toward the space bars that they wouldn’t cause strain, but it’s hard to know for sure without trying a real one. (Darn you, global shortages and shipping delays!)
There are all sorts of reasons to build your own keyboard, and we would argue that the more custom the layout, the easier it is to justify the time and expense. At least, that’s what we’re going with for this post about [GoldenSights]’ big, beautiful custom ortholinear called Nearer, as in nearer to perfect. Just look at this battleship!
[GoldenSights] has long wanted a mechanical keeb, but has never been into any of the commercial offerings. That goes double since none of them seem to have a vertical Home/End cluster, which [GoldenSights] has become quite attached to thanks to a space-saving Logitech rectangle keeb. But if you’re going to make your own keyboard, you should go all out, right? Right. So [GoldenSights] started by adding another 12 F keys and making it ortholinear. Then things got personal with an extra Backspace where Num Lock usually lives, and dedicated keys for switching between English, Korean, and Chinese.
[GoldenSights] wanted USB-C and so they used an Elite-C microcontroller, but there’s one big problem — it only has 24 pins, and according to the matrix math, the board needs 27 total. Rather than using an I/O expansion chip or a second microcontroller, they wired it up as duplex matrix. This is an alternative way of wiring up a matrix so that it’s closer to being square by doubling up the rows and halving the number of columns.
We don’t think [GoldenSights] gives themselves enough credit here. They say that they lean toward calling it assembly rather than a build, but we disagree with that assessment. [GoldenSights] broke in this giant keeb with giant write-up of the build, so go see for yourself. There’s a ton of build pictures and a fair amount of hot glue, so be warned.
Let’s talk about those keycaps for a second. The space bar was supposed to be black PBT like the others, but the keycap manufacturer didn’t have a 6u space bar in black and sent a gray one instead. Honestly, we like the way it looks. And we love that [GoldenSights] painstakingly laid out the keys on foam board before committing to a laser-cut metal switch plate.
Maybe you’re not ready to take the leap into a full-on ergonomic split keyboard. That’s okay, that’s cool, that’s understandable. They’re weird! Especially ones like my Kinesis Advantage with the key bowls and such. But maybe your poor pinkies are starting to get tired and you’re ready to start using your thumbs for more than just the space bar. Or you want to be able to type ‘c’ properly, with your middle finger.
In that case, the TypeMatrix could be the keyboard for you. Or maybe for travel you, because it’s designed as a quasi-ergonomic, orthonormal layout travel keyboard to pair with your laptop, and as such it sits directly over a laptop keyboard without blocking the track pad. (How do people use those things, anyway?)
Of course, you could use this as a desktop keyboard as well, although it’s unfortunate that Control and Shift are stuck on the pinkies. More about that later.
When I saw this keyboard on eBay, I was attracted by two things: the layout, and the dedicated Dvorak light. (And, let’s be honest — the price was right.) I’ve always found myself generally turned off by chocolate bar-style ortholinear keebs because they’re so incredibly cramped, but this one seemed a more acceptable because of the slight split.
The first thing I noticed was the fantastic number pad integration. The different colored keycaps are a nice touch, because the gray makes the number pad stand out, and the red Delete is easy to find since Num Lock is squatting in the upper right corner. Why does Delete always feel like an afterthought on compact keebs? I also like the location of the arrows, and it makes me think of the AlphaSmart NEO layout. Unfortunately, it comes at the cost of burying the right hand Enter down in no-man’s land where you can’t exactly hit it blindly with great accuracy right away. If only you could swap Shift and Enter without messing up the number pad!
Oh, sure, there have been a few cube-shaped PCs over the years, like the G4 and the NeXT cube. But can they really be called cubes when the display and the inputs were all external? We think not.
[ikeji] doesn’t think so either, and has created a cube PC that puts them all to shame. Every input and output is within the cube, including our favorite part — the 48-key ortholinear keyboard, which covers two sides of the cube and must be typed on vertically. (If you’ve ever had wrist pain from typing, you’ll understand why anyone would want to do that.) You can see a gif of [ikeji] typing on it after the break.
Inside the 3D printed cube is a Raspberry Pi 4 and a 5″ LCD. There’s also an Arduino Pro Micro for the keyboard matrix, which is really two 4×6 matrices — one for each half. There’s a 6cm fan to keep things cool, and one panel is devoted to a grille for heat output. Another panel is devoted to vertically mounting the microcontrollers and extending the USB ports.
When we first looked at this project, we thought the tiny cube was a companion macro pad that could be stored inside the main cube. It’s really a test cube for trying everything out, which we think is a great idea and does not preclude its use as a macro pad one of these days. [ikeji] already has plenty of plans for the future, like cassette support, an internal printer, and a battery, among other things. We can’t wait to see the next iteration.
[Blake]’s interest in building keyboards happened naturally enough — he was looking for a new project to work on and fell into the treasure chest that is the mechanical keyboard community. It sounds like he hasn’t built anything but keyboards since then, and we can absolutely relate.
We particularly like the double rainbow ribbon cable wiring method [Blake] used to connect each row and column to the controller. It looks beautiful, yes, but it’s also a great way to maintain sanity while programming and troubleshooting.
Keyboard builds can look daunting, even at 40% of standard size. But as [Blake] discovered, there are some really good guides out there with fantastic tips for hand-wiring in small spaces. And now there is another well-written guide with clear pictures to point to.
Once upon a time, keyboards were something that you took with you from computer to computer, because most of them were built quite nicely. After a few dark decades of membrane keyboards being the norm, the rise of the mechanical keyboard community has shined a light on what is possible with open source designs. Anyone can join in, because quality clackers now exist on every level, whether you want to design the perfect split ortho with OLEDs, rotary encoders, and rear view mirrors, or just want to fork over some money and get to punching switches.
Building your own keyboard doesn’t have to be daunting. It can be as easy or as involved as you want. There’s still a fair amount of soldering simply because it’s a keyboard. But there are plenty of options if you don’t want to do a whole lot beyond soldering switches (or hot swap sockets!) and putting a case together.
The interesting thing about the JNAO is the breakaway row of keys on the bottom. The standard grid is 12×5, but if you don’t need the dedicated number row along the top like [Jared], you’re not stuck with it. And you’re not stuck with the default layout, either. Flashing to a standard Planck layout didn’t go as easily as [Jared] might have liked, but we think he was wise to get the firmware squared away before ever turning on the soldering iron.
They say you should never cheap out on anything that comes between you and the ground, like tires, shoes, and mattresses. We would take that a little further into the 21st century and extend it to anything between you and work. In our case, ‘buy nice or buy twice’ includes keyboards and mice.
That’s not all [Marcus] did to make the dactyl his own — it also has a modified full-fat base that gives him all the room in the world to wire up the keyswitch matrix compared to the original streamlined design.
Instead of the usual Teensy, Pro Micro, or Proton-C, the pterodactyl has a Feather 32u4 in its belly. [Marcus] is clacking on Holy Panda switches which we’ve been meaning to try, and individual PCBs for each switch, which seems like it might negate gluing the switches in place so they survive through keycap changes. Check out [Marcus]’ write-up to see what he learned during this build.
This isn’t the first modified dactyl we’ve seen flying around here, and it won’t be the last. Here’s one with a dual personality — both halves can work together or alone.