that's right, we don't want to do params = { ... } because then we're hardcoding the implementation and it becomes very coupled. The benefit of doing it like in my examples is that you can change the method signature and still automatically capture all keyword parameters.

Another important MicroJS attribute is independence. Ember, Backbone—even Bootstrap to a degree–have hard dependencies on other libraries. For example, all three rely on jQuery. A good MicroJS library stands by itself with no dependencies. There are exceptions to the rule, but in general, any dependency is another small MicrojJS library.

Now I just need to figure out how to decouple this ball of mud

these two functions >>= and eta were designed to simplify add, but they clearly do not depend on the specifics of add in any way, just the Maybe type

Whatever data from the outside is needed in the activity has to be passed explicitely into the activity’s call method.

Operations don't know about HTTP or the environment. You could use an operation in Rails, Hanami, or Roda, it wouldn't know.

By default the current directory is used, but it's recommended to pass a value in your configuration. This makes your configuration independent from CWD (current working directory).

You may want to decouple a validation schema definition from its form ui.

All validators can be used independently. Inspried by functional programming paradigm, all built in validators are just functions.

FormValidation.validators.creditCard().validate({

FormValidation.formValidation(formElement

that a better and cleaner approach would be to use computed properties and a validation library that is decoupled for the UI (like hapi/joi).

I'm personally open to any other solutions, especially in how we might be able to untie from React, but, for now, inline-XML markup (JSX) is OK with me.

or when decoupling from the rest of the template would be nontrivial.

Solid supports templating in 3 forms JSX, Tagged Template Literals, and Solid's HyperScript variant.