2025-11-06 20:44:27
I’ve heard so much about HHKB, so I’m overly excited to have finally tried it.
No, I didn’t buy another keyboard (yet). I’m happily using my first and second custom builds at work and at home respectively. It is just one of my colleagues has been so kind to share his HHKB Professional Hybrid Type-S.
I’ve been using it for several days in the office, and wanted to share my impression.
HHKB HYBRID Type-S Snow Keyboard © PFU
First of all, it looks great. Snow-white, with blank keycaps, it is clean and minimal. Type-S stands for silent, and it is quiet, but I find my RD75 even quieter.
The Topre switches are one of the reasons this keyboard is so hyped. And they are interesting. I certainly wouldn’t mind typing on them even longer. But they are not enough to make a switch.
The main issue is that such layout is not for me. The chords to press ⌃⇧Tab, for example, or simply arrow keys are awkward. Of course, there are many blog posts claiming that one can get used to it. Sometimes, they mean after a few days of weeks, while others are talking about a year. And I’m absolutely not convinced that it is worth it.
The biggest issue, however, was that HHKB would never be the only keyboard I use. I’m pretty happy with my existing set, and I quite often need to type on the go on the MacBook’s built-in keyboard. Re-learning arrows and Ctrl position many times per day is a no-go for me.
So, thanks and it was a great pleasure, but I’m back to my old good friends.
And, yes, I struggled all the way through and typed, edited, and published this entire post on the HHKB.
This is post 36 of #100DaysToOffload
2025-08-01 04:02:11
It ain’t much but it’s honest work.
31 days
This is post 35 of #100DaysToOffload
2025-07-18 17:14:25
My favorite Lufthansa flight.
It’s a shame that when I once flew to Toulouse, I didn’t take this flight.
And the second one.
Image: LEGO
This is post 34 of #100DaysToOffload
2025-07-04 01:50:12
I’ve read on The Verge today that new Lorde’s album “Virgin” causes troubles with many CD players. I don’t listen to her music, and I last played a CD in my old car many years ago, so maybe I would have skipped the news. Until I read about the reason.
Lorde Virgin CD. Image: Lorde
The issue most players had with the CD was that it was almost completely transparent. They just didn’t understand that it was in, or refused to pull it in, as they didn’t recognize the disk.
I burst up in laughter because I had a similar issue before. When I was driving that car, I mentioned earlier. I replaced the head unit by that time though, so the issue was not with a CD.
We had a vacation in Croatia and were driving on a highway there when we stopped at a toll booth. Croatia had joined the EU but hadn’t yet switched to Euro. They were still using Kuna. Not a problem at all when paying with a credit card with a good conversion rate. And I had one.
I inserted it into the toll payment machine. It pulled it in, and… nothing happened. The barrier didn’t open, and after some delay, the machine asked to insert the card again. The queue behind our car had started to build up already. I had no other choice but to call support.
The support answered pretty quickly. After I explained the situation, they requested the info about the card.
“Uhm, it is a MasterCard” – I answered. I was baffled.
“No, what color?” – the support agent asked for clarification.
What a strange question I thought, but I replied: “Uhm, it has no color. It is transparent.”
My transparent card. Image: N26
“Okay” – I heard back, and soon afterward, something clicked inside the machine, and it ejected the card.
“Please use a different card” – asked the support agent and disconnected. Good that I had another one.
What’s the moral of the story? Transparency is good until it creates troubles.
This is post 33 of #100DaysToOffload
2025-06-05 18:27:17
A few years have gone since I’ve built my first custom mechanical keyboard. It was inevitable that I would want to build another one. Especially given how the market has advanced since then.
The keyboards are now much better than two years ago. It is now common for CNC aluminum keyboards to have tri-mode (Bluetooth, wireless via proprietary dongle, and USB-C) connectivity, which was deemed impossible back then. All modern keyboards come with decent stock stabilizers, better materials and build quality.
And my new keyboard has a pretty unique feature: its case is held together via ball-joint magnetic latches. The daughter-board connected via a magnetic connection as well. This allows quickly opening and re-assembling the keyboard. There is no single screw in there.
But as much cool as this feature is, as rare I will likely need it. As I said, I’m fully satisfied with the factory build and don’t want to change anything.
Except for switches and keycaps, of course.
In fact, it all started with keycaps. I enjoyed MT3 profile keycaps from my previous keyboard and was following its creator Matt3o for a while already. When he announced his new project MTNU, I immediately knew what keycaps I would use for my new build.
The new profile is lower, compared to MT3 these are much closer to “normal” keycaps. Still, it features a round key top that I like so much and homing keys, which are just deeper and don’t have an itchy ridge. And the new font, designed from scratch specifically for these keycaps.
So, as soon as I found the right color scheme, I joined a group buy run by Obolotzky (I can highly recommend, by the way). Then, however, there have been almost 6 long months of waiting, but these are the game rules, and I’ve been prepared for it.
As for switches, I again wanted silent tactile switches. For better or worse, I couldn’t find Boba U4 Silents in stock. So I needed to choose some others, and my choice fell upon Outemu Cream Yellow Pro Silent Tactile switches.
They are a bit lighter and even less loud (I couldn’t imagine it is possible). The tactile bump is exactly as I like. I’m very pleased with the combination of the keycaps and switches I ended up with.
And, yes, the board itself! It is the Womier RD75. It is a new player in the field, but they are already quite popular because they offer high-quality boards for affordable prices.
The keyboard sounds very pleasant out of the box, though I can’t work more than 5 minutes when the keyboard is so loud. It is just too distracting for me.
There were some problems with the keyboard, however.
First, it came with a malfunctioning switch, but they put three spares in the box, so it wasn’t a big issue. And I replaced all switches anyway.
Second, some modifier combinations didn’t work when I switched to Mac mode. This was mitigated by switching back to Windows mode and swaping left Alt and Win keys. Didn’t find any other issues with this setup.
The third issue that bothered me the most was the Caps Lock delay, which macOS considered as long-press. I’m using Caps Lock to switch input methods, so after each switch it toggled Caps Lock, making the keyboard unusable. Luckily, I found a solution here as well. I only needed to disable NKRO, which purpose I anyway didn’t fully understand.
The fourth and final issue was that in the default layout, there is a “handy” shortcut to factory reset the keyboard. Right near a shortcut that shows battery status and turns lighting on and off. Needless to say, I pressed it accidentally after I applied all above customizations and needed to reapply them.
The biggest disappointment so far is that although the keyboard is configurable with VIA and runs on QMK, it doesn’t support flashing custom QMK firmware, as the source code they provided doesn’t compile. I hope that they will eventually fix this and supply the source code as they are obliged under the terms of GPL.
So here is Victor’s Mk2:
Can’t wait to build the next one.
PS. This blog post was typed in its entirety on this keyboard, of course.
This is post 32 of #100DaysToOffload
2025-05-29 17:09:14
Another year has flown by, and I again had the pleasure of attending the KotlinConf in Copenhagen. It is the conference I now look forward to every year. And it was my third time in a row!
KotlinConf 2025 Keynote
This time, my team had a major goal ahead of it: we were on to release Compose Multiplatform iOS target as stable. And folks did a great job to do that. Somewhat unexpectedly for me, the release itself did not excite people much. Seemingly many already considered our iOS support as good enough for their use cases as we’ve already seen many apps using it in production.
Instead, we’ve got a lot of questions on how to convince their iOS subteams to adopt Kotlin and Compose Multiplatform. That’s great, as it proves that the technology is mature enough, and nobody who actually tried it has any doubts that adopting it is the right decision.
I volunteered to help with the KotlinConf app this year and enjoyed using Compose Multiplatform in a real-world project. JetBrains’ engineering culture relies a lot on dogfooding, and this was a perfect way to try the framework first hand.
KotlinConf App 2025 edition
The app received a lot of positive feedback during the conference and helped us to improve the framework during its development.
It was also my first time delivering a workshop at the conference. I wouldn’t do it myself, but when colleagues I respect asked me to, I could not refuse.
It went pretty well overall, but as always, we already have ideas how to improve it next time.
Both the workshop and KotlinConf wouldn’t be possible without Márton, once again kudos to him! Kotlin and JetBrains are very lucky to have him on our side.
For the first time in the conference history, the next year’s location was revealed at the closing panel, and it is going to be Munich 🥨, my hometown.
See you next year in Bavaria!
This is post 31 of #100DaysToOffload
