Originally posted on the mailinglist here. Mostly copied it here so I can add it to Pocket.
Here are some problems/limitations of existing OO/GF systems that I don't intend to repeat:
A) They provide only a single declaration point for all superclasses of a class B) They consider the local declaration order of superclasses to be
More context: https://twitter.com/martinklepsch/status/810483946597158912
$ sudo dtruss login
dtrace: system integrity protection is on, some features will not be available
dtrace: failed to execute login: dtrace cannot control executables signed with restricted entitlements
In my ~/.tmux.conf I had a line like this:
set-option -g default-command "reattach-to-user-namespace -l fish"
| ;; This was an earlier attempt using clojure.spec. I discarded it for reasons I don't remember. | |
| (ns forms.core | |
| (:require | |
| #?(:cljs [cljs.spec :as s] | |
| :clj [clojure.spec :as s]))) | |
| ;; (s/def ::form-state | |
| ;; {::value s/Any | |
| ;; ::initial-value s/Any | |
| ;; ::errors s/Any |
A note on terminology: There are a lot of things with similar meanings/use-cases around: subscriptions, reactions, derived atoms, view models.
I'll introduce another to make things even worse: derivative. A derivative implements IWatchable and it's value is the result of applying a function to the value of other things (sources) implementing IWatchable. Whenever any of the sources change the value if the derivative is updated.
Let's assume you're hooked about the idea of storing all your application state in a single atom (db). (Why this is a great idea is covered elsewhere.)
Most of your components don't need the entirety of this state and instead receive a small selection of it that is enough to allow the components to do their job. Now that data is not always a subtree (i.e. (get-in db ...)) but might be a combination of various parts of your state. To transform the data in a way that it becomes useful for components you can use a function: `(f @
| (ns oc.bot.sqs | |
| (:require [amazonica.aws.sqs :as sqs] | |
| [com.stuartsierra.component :as component] | |
| [manifold.stream :as s] | |
| [manifold.time :as t] | |
| [manifold.deferred :as d] | |
| [environ.core :as e])) | |
| (def creds | |
| {:access-key (e/env :aws-access-key) |
| ;; Auto-scrolling ============================================================== | |
| (defn scroll! [el start end time] | |
| (.play (goog.fx.dom.Scroll. el (clj->js start) (clj->js end) time))) | |
| (defn scrolled-to-end? [el tolerance] | |
| ;; at-end?: element.scrollHeight - element.scrollTop === element.clientHeight | |
| (> tolerance (- (.-scrollHeight el) (.-scrollTop el) (.-clientHeight el)))) | |
| (defn autoscroll-list [{:keys [children class scroll?] :as opts}] |
| // The flag object shares a lot of common traits with the media | |
| // object; its sole purpose is displaying image- and text-like content | |
| // side-by-side. Where the flag object differs, however, is its ability | |
| // to vertically align the image and text to the tops, middles or bottoms | |
| // of each other. | |
| // | |
| // http://csswizardry.com/2013/05/the-flag-object/ | |
| .flag | |
| display: table |
| (defn same-val [m] | |
| (-> (fn [nm [k v]] | |
| (let [in-other? (-> (dissoc m k) vals set)] | |
| (if (in-other? v) | |
| (assoc nm k v) | |
| nm))) | |
| (reduce nil m))) | |
| (defn dir-scoper |
| #!/usr/bin/env boot | |
| (require '[boot.pod :as pod]) | |
| (defonce pods | |
| (pod/pod-pool (get-env))) | |
| (defn -main [& args] | |
| (loop [i 0] | |
| (let [c-pod (pods :refresh)] |
| ~/c/boot-fileset-perf boot watch modify-random | |
| Starting file watcher (CTRL-C to quit)... | |
| 1 files in fileset | |
| Elapsed time: 0.156 sec | |
| 21 files in fileset | |
| Elapsed time: 0.085 sec |