All I want is a quality split mechanical keyboard with Function keys. I use an IDE all day, I don't want to pull quadruple buckies every time I debug. The Matias Ergo Pro is almost perfect, but I had two of them and they both failed within one year. I had one of each switch type (low force and regular) - both were missing some button presses and repeating other button presses.
You can get a QMK keyboard and create a function key layer.
Thoughts on Mechanical Keyboards and the ZSA Moonlander
11–20 of 283 posts
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#12All I want is a quality split mechanical keyboard with Function keys. I use an IDE all day, I don't want to pull quadruple buckies every time I debug. The Matias Ergo Pro is almost perfect, but I had two of them and they both failed within one year. I had one of each switch type (low force and regular) - both were missing some button presses and repeating other button presses.
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#13All I want is a quality split mechanical keyboard with Function keys. I use an IDE all day, I don't want to pull quadruple buckies every time I debug. The Matias Ergo Pro is almost perfect, but I had two of them and they both failed within one year. I had one of each switch type (low force and regular) - both were missing some button presses and repeating other button presses.
Kinesis Freestyle Pro? I've got the non mechanical version (mechanical wasn't available when I purchased) and it's held up for many years. It's a great keyboard IMO.
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#14All I want is a quality split mechanical keyboard with Function keys. I use an IDE all day, I don't want to pull quadruple buckies every time I debug. The Matias Ergo Pro is almost perfect, but I had two of them and they both failed within one year. I had one of each switch type (low force and regular) - both were missing some button presses and repeating other button presses.
The author's whole point here is that QMK (or ZMK, which I use) lets you customize it to exactly your own needs!
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#15I have two moonlanders but wound up giving up because I just couldn't adapt to it. And when writing code, finding the symbols like {, =, }, and other common coding ones was just too difficult to retain muscle memory. I tried many layouts, I tried to make my own, and at the end of the day it was just too different. I wish I had a better experience. Any recommendations?
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#16Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#17All I want is a quality split mechanical keyboard with Function keys. I use an IDE all day, I don't want to pull quadruple buckies every time I debug. The Matias Ergo Pro is almost perfect, but I had two of them and they both failed within one year. I had one of each switch type (low force and regular) - both were missing some button presses and repeating other button presses.
One is to replace the switches. If they're hot swappable then it's easy. If they're not, it's hard -- but easy if you're willing to spend money on a desoldering iron. Depending upon your feelings here, I would consider it maintenance to keep it going if you love it -- particularly if you use it to prevent RSI.
A quick look shows matias does sell replacement switches -- which is usually the thing to go. Springs, crud, etc end up in the switches. Sometimes you can tear them apart to fix them, sometimes it's easier to toss them and replace them.
The typical desoldering tool for keyboards is something like this:
https://www.amazon.com/ENGINEER-Engineer-Solder-Suction-SS-0...
They also have things like this that are maybe more functional than trying to do it two handed:
https://www.amazon.com/zycllycx-Electric-Automatic-Desolderi...
But the hakko is the gold standard here. If you have keyboards you absolutely love but are soldered, this is the way to go.
https://www.amazon.com/Hakko-FR-301-Portable-Desoldering-Too...
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#18I have two moonlanders but wound up giving up because I just couldn't adapt to it. And when writing code, finding the symbols like {, =, }, and other common coding ones was just too difficult to retain muscle memory. I tried many layouts, I tried to make my own, and at the end of the day it was just too different. I wish I had a better experience. Any recommendations?
- Spend time practicing away from important coding tasks (e.g. gaming, writing, a side project, a one-off script, etc.). Being able to learn in a forgiving environment, outside of deadlines, gives you the space to allow mistakes and time to correct them
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#19I have two moonlanders but wound up giving up because I just couldn't adapt to it. And when writing code, finding the symbols like {, =, }, and other common coding ones was just too difficult to retain muscle memory. I tried many layouts, I tried to make my own, and at the end of the day it was just too different. I wish I had a better experience. Any recommendations?
The default layers are pretty good, but I found programming the keys/layers to what made sense to me to be more beneficial. I use the heat map to see which keys get the most milage and program layers around that. Then I only program a few new keys at a time and get a feel for things. My words-per-minute went down initially but now it is back.
I have been tweaking my layout for about a month and am close to being happy with it. I've set myself a milestone that when I don't make any tweaks for 6 months I will buy custom keycaps that have my exact symbols/layers on each key.
Re: Thoughts on Mechanical Keyboards and the ZSA Moonlander
#20All I want is a quality split mechanical keyboard with Function keys. I use an IDE all day, I don't want to pull quadruple buckies every time I debug. The Matias Ergo Pro is almost perfect, but I had two of them and they both failed within one year. I had one of each switch type (low force and regular) - both were missing some button presses and repeating other button presses.
I find one modifier plus a home-row key to be much more comfortable than reaching several rows up for an F-key. The author's whole point here is that QMK (or ZMK, which I use) lets you customize it to exactly your own needs!
Just for an example off the top of my head, in JetBrains IDEs the shortcut for hiding all tools is Ctrl-Shift-F12.