And I have to say that trying to program it without UHK agent is PAINFUL, even though there is a GUI available for this other thing. You guys really did a great job with designing the user experience when programming the UHK.
6 Likes
Thank you! We’ve been developing Agent and the firmware since early 2016 with a heavy focus on usability. We’re still going strong, and we’re glad it shows.
4 Likes
Yeah it’s quite sad to see ~2 devs run circles around entire very old OSS communities as someone who lurks Github. Can somewhat reliably say UHK firmware and macros etc. are the best of them all as a heavy programmer.
1 Like
Yeah it’s quite sad…
Not at all.
Agent and the UHK firmware were built with a customer focus from the start. ZMK, according to this article, came into being to scratch “a personal itch”.
It is not at all sad to see “~2 devs run circles around the entire very old OSS communities.” Rather, it’s impressive that they planned so well. I’m sure some of their architecture decisions early-on made this possible.
Agent and the UHK firmware were built with a customer focus from the start.
Well, right… 
Agent definitely was, but when it comes to the macro engine… when I forked the firmware and started hacking it, it too was to deal with personal dissatisfaction. The macro language is a mess. It was not designed - at the beginning it was only a way to trigger firmware code without having to modify Agent via single word commands, and as time went, it snowballed into what it is now by smallest possible “improvements”.
1 Like
Speaking as one of the Ancient Ones (lurking in the void since the early days of UHK’s creation);
It’s certainly been impressive to witness the UHK’s miraculous evolution, as it’s continuously weaved by the hands of a minute pantheon of Intelligent Improvisors.
Wow, I need some sleep 
Is it just me, or did that sound like I was about to write a review for some British prog-rock group?
Anyway, “Minute Pantheon of Intelligent Improvisors” is a great band name…
2 Likes