Skip to main content

Keychron Q1 vs GMMK Pro: A Comparative Review


Mechanical keyboards have become increasingly popular in recent years, and with a plethora of options available on the market, choosing the right keyboard can be a daunting task. In this blog post, I will be comparing two highly rated 75% mechanical keyboards - the Keychron Q1 and the GMMK Pro.

Build Quality and Sound Profile

The GMMK Pro has a stiff plate and does not move, making it suitable for mechanical switches that bottom out. This creates a noisy ring on the brass plate, especially with double-shot SA caps that produce a higher pitched metallic sound when bottoming out. The Q1, on the other hand, features a plate that sits on spongy spacers, which absorb the shock from typing, resulting in a smoother and softer typing experience. The plate also moves slightly when bottoming out, which is a unique feeling.

When it comes to sound, both keyboards are not significantly different, but the GMMK Pro tends to be a little more hollow due to its stiffer plate. The Keychron Q1, however, has brighter RGB out of the box and more options to customize it.

Remapping and Customization

Both keyboards are highly customizable, with the Keychron Q1 using VIA, which makes remapping the layout effortless. The GMMK Pro has the Glorious Core, which doesn't have as many options as VIA but does work well with QMK after recent updates. In my personal experience, I didn't need to remap the GMMK Pro after updating its firmware, but I did remap the Keychron Q1 to suit my personal preference.

Keycaps and Plate Material

The GMMK Pro has a brass plate and is compatible with Glorious Pandas and thick SA profile keycaps, making it ideal for a noisy typing experience. The Keychron Q1, on the other hand, is compatible with a wide range of keycaps, including SAs, which can be challenging to arrange due to their height variation and orientation from row to row.


Both the Keychron Q1 and the GMMK Pro are high-quality mechanical keyboards that cater to different preferences. The GMMK Pro is ideal for those who enjoy a noisy typing experience with brass plates and thick SA profile keycaps, while the Keychron Q1 is more suited for those who prefer a smoother and softer typing experience with brighter RGB lighting and a wider range of compatibility with keycaps. Ultimately, the choice between the two depends on personal preference and the type of experience you are looking for in a mechanical keyboard.


Popular posts from this blog

Dev OnCall Patterns

Introduction Being On-Call is not easy. So does writing software. Being On-Call is not just a magic solution, anyone who has been On-Call can tell you that, it's a stressful, you could be woken up at the middle of the night, and be undress stress, there are way's to mitigate that. White having software developers as On-Calls has its benefits, in order to preserve the benefits you should take special measurements in order to mitigate the stress and lack of sleep missing work-life balance that comes along with it. Many software developers can tell you that even if they were not being contacted the thought of being available 24/7 had its toll on them. But on the contrary a software developer who is an On-Call's gains many insights into troubleshooting, responsibility and deeper understanding of the code that he and his peers wrote. Being an On-Call all has become a natural part of software development. Please note I do not call software development software engineering b

SQL Window functions (OVER, PARTITION_BY, ...)

Introduction When you run an SQL Query you select rows, but what if you want to have a summary per multiple rows, for example you want to get the top basketball for each country, in this case we don't only group by country, but we want also to get the top player for each of the country.  This means we want to group by country and then select the first player.  In standard SQL we do this with joining with same table, but we could also use partition by and windowing functions. For each row the window function is computed across the rows that fall into the same partition as the current row.  Window functions are permitted only in the  SELECT  list and the  ORDER BY  clause of the query They are forbidden elsewhere, such as in  GROUP BY ,  HAVING  and  WHERE  clauses. This is because they logically execute after the processing of those clauses Over, Partition By So in order to do a window we need this input: - How do we want to group the data which windows do we want to have? so  def c

Functional Programming in Scala for Working Class OOP Java Programmers - Part 1

Introduction Have you ever been to a scala conf and told yourself "I have no idea what this guy talks about?" did you look nervously around and see all people smiling saying "yeah that's obvious " only to get you even more nervous? . If so this post is for you, otherwise just skip it, you already know fp in scala ;) This post is optimistic, although I'm going to say functional programming in scala is not easy, our target is to understand it, so bare with me. Let's face the truth functional programmin in scala is difficult if is difficult if you are just another working class programmer coming mainly from java background. If you came from haskell background then hell it's easy. If you come from heavy math background then hell yes it's easy. But if you are a standard working class java backend engineer with previous OOP design background then hell yeah it's difficult. Scala and Design Patterns An interesting point of view on scala, is