Skip to content

Instantly share code, notes, and snippets.

@PastaJ36

PastaJ36/rgb-and-analog-sdk-split.md

Created February 28, 2019 03:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save PastaJ36/a98ce9937059917e85267b0eca37e052 to your computer and use it in GitHub Desktop.
Save PastaJ36/a98ce9937059917e85267b0eca37e052 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
rgb-and-analog-sdk-split.md

Why is there a split between the Wooting analog and RGB SDK?

The main goal of Wooting is to make analog keyboards an industry standard, with the analog SDK being the main driver. If you just look at Wooting keyboards in itself it would make sense to combine them into one. One system that can control everything. But this way we set ourselves up for a problem.

The peripheral market right now already has many RGB systems. Most closed and some starting to open up a bit. Even though the RGB systems have many flaws and are not compatible at all, companies have already decided on their systems.

Now imagine you’re a company deciding if you want to adopt this new analog thing: would you want there to be a RGB part in it that competes with your own system? That’s why we decided to keep it split. The analog SDK should be it’s own pure thing that is just focussed on one thing, making analog keyboards standard in the industry. The RGB SDK is just a cool separate Wooting thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment