Skip to content

Instantly share code, notes, and snippets.

@andys8
andys8 / fantasyland_spec_cheatsheet.md
Created Aug 6, 2017
A cheatsheet to have the fantasy land algebraic specification at a glance
View fantasyland_spec_cheatsheet.md

Fantasy Land Specification Cheatsheet

Algebras

Algebra Methods
Functor map
Apply ap, map
Applicative of, ap, map
Chain chain, ap, map
@evancz
evancz / Architecture.md
Last active Jun 28, 2021
Ideas and guidelines for architecting larger applications in Elm to be modular and extensible
View Architecture.md

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

  1. There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo
@honza
honza / gist.md
Created Jun 30, 2013
Clojure vs Haskell
View gist.md

Haskell vs Clojure

The JSON data is in the following format

{
    "Genesis": {
        "1": {
            "1": "In the beginning..." ,
            "2": "..."