Skip to content

Instantly share code, notes, and snippets.

@retro

retro/why-keechma.md

Created May 31, 2016 23:28
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 retro/bc424b731258abb54b0a610c4a39b8c0 to your computer and use it in GitHub Desktop.
Save retro/bc424b731258abb54b0a610c4a39b8c0 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
why-keechma.md

Why Keechma?

Here are some of my thoughts related to Keechma and why you should try it out…

Unlike the “Keechma Design Decisions” post, this one is purely subjective, and appealing to your emotions.

Globals

Globals are bad.

Router

Routes should be treated like data. You shouldn’t care about the hierarchy, you should care about the data they represent.

Controllers

Controllers exist for two reasons:

  1. They mediate transformation from the route to the app state
  2. They react to user commands and act as a bridge between the UI and the domain code

If your framework doesn’t have a controller like construct, you’re going to reinvent it.

EntityDB

EntityDB is the best (default) store for your data. It takes care of the duplicates, relationships and is automatically replicated to the UI. Sweet!

UI System

This one is the hardest to explain. Keechma UI system allows you to build independent components. They can declaratively declare their dependencies, which allows you to build (independent) systems of related components. (I need a better pitch for this)

Conclusion

If you think that Keechma is built on sound beliefs, make sure you try it out!

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