A declarative state and side effects management solution for popular JavaScript frameworks

Writing declaratively:

<h1 class="header">Hello</h1>

Compared to imperatively:

const h1 = document.createElement('h1')
h1.className = 'header'

It makes perfect sense for us to write our UIs in a declarative manner. The reason is that we need to reuse UI elements and compose them together in different configurations. One can also claim that declarative code reads better, not because it is less syntax, but because you only describe what you want, not how you want it.

But what about our business logic, can we get the same benefits there?

Writing declaratively:

  set(state`isLoadingUser`, true),
  httpGet('/user'), {
    success: set(state`user`, props`user`),
    error: set(state`error`, props`error`)
  set(state`isLoadingUser`, false),

Compared to imperatively:

function getUser() {
  this.isLoading = true
    .then((user) => {
      this.data = user
      this.isLoading = false
    .catch((error) => {
      this.error = error
      this.isLoading = false

You might think this example tries to highlight “less lines of code”, but that is just a result of reaching for the following properties:

  • Composability
  • Readability
  • Reusability
  • Testability

All these properties makes better code and the declarative approach inherits all of them by default, where the imperative approach does not. Read on to learn more about how Cerebral enforces these properties in your codebase.