Pros of nrfmicro

• Wireless capability using nRF52 microcontroller
• Smaller form factor and lower power consumption
• Supports Bluetooth connectivity for multiple devices

Cons of nrfmicro

• More complex setup and configuration process
• Limited compatibility with some keyboard firmware
• Potentially higher cost due to specialized components

Code Comparison

nrfmicro:

#define PIN_SERIAL_RX 8
#define PIN_SERIAL_TX 6
#define PIN_SPI_MISO 14
#define PIN_SPI_MOSI 13
#define PIN_SPI_SCK 15

crkbd:

#define MATRIX_ROW_PINS { D4, C6, D7, E6 }
#define MATRIX_COL_PINS { F4, F5, F6, F7, B1, B3 }
#define DIODE_DIRECTION COL2ROW

The nrfmicro code defines pins for serial and SPI communication, reflecting its wireless capabilities. The crkbd code defines matrix row and column pins for a traditional wired keyboard setup.

nrfmicro focuses on wireless functionality and compact design, making it suitable for portable, low-power applications. crkbd, on the other hand, offers a more straightforward wired setup with broader firmware compatibility. The choice between them depends on specific project requirements, such as wireless functionality, power consumption, and ease of configuration.

Pros of Lily58

• More keys (58 vs 42), offering a layout closer to traditional keyboards
• Includes number row, reducing the need for layer switching
• Easier transition for users coming from standard keyboards

Cons of Lily58

• Larger footprint, less portable than Crkbd
• Potentially less ergonomic due to increased finger movement
• More complex assembly process with additional components

Code Comparison

Lily58 (config.h):

#define TAPPING_FORCE_HOLD
#define TAPPING_TERM 100
#define IGNORE_MOD_TAP_INTERRUPT

Crkbd (config.h):

#define TAPPING_FORCE_HOLD
#define TAPPING_TERM 200
#define IGNORE_MOD_TAP_INTERRUPT
#define PERMISSIVE_HOLD

Both projects use similar configuration options, but Crkbd includes an additional PERMISSIVE_HOLD setting and a longer tapping term. This suggests that Crkbd may have a more refined tap-hold behavior, potentially offering a smoother typing experience for advanced users.

The core differences between these projects lie in their physical layouts and design philosophies rather than their firmware configurations. Lily58 aims to provide a more familiar layout for newcomers to split keyboards, while Crkbd focuses on minimalism and portability.

Pros of qmk_firmware

• Supports a wide range of keyboard layouts and models
• Extensive documentation and community support
• Regular updates and active development

Cons of qmk_firmware

• Steeper learning curve for beginners
• Requires more setup and configuration

Code Comparison

crkbd (keymap.c):

const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
  [_QWERTY] = LAYOUT(
    KC_TAB,  KC_Q,    KC_W,    KC_E,    KC_R,    KC_T,
    KC_LCTL, KC_A,    KC_S,    KC_D,    KC_F,    KC_G
  ),
};

qmk_firmware (keymap.c):

const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
    [0] = LAYOUT(
        KC_ESC,  KC_Q,    KC_W,    KC_E,    KC_R,    KC_T,
        KC_TAB,  KC_A,    KC_S,    KC_D,    KC_F,    KC_G
    ),
};

The code structure is similar, but qmk_firmware offers more flexibility in defining layers and key functions. crkbd focuses specifically on the Corne keyboard layout, while qmk_firmware provides a framework for various keyboard designs.