📄	.gitignore
📄	LICENSE
📄	NOTES.md
📄	README.md
📄	avatar.png
📄	catstack.jpg
📄	dogstack.jpg
📄	engelbart.jpg
📄	enspiral.png
📄	example.js
📄	follow_your_dreams.png
📄	git-ssb-screenshot.png
📄	index.css
📄	index.html
📄	index.js
📄	luddite.jpg
📄	morpheus-cat.png
📄	package-lock.json
📄	package.json
📄	patchwork-screenshot.jpg
📄	patchwork.png
📄	rabbit-hole.jpg
📄	root-systems.jpg
📁	stuff
📁	test
📄	training-wheels.jpg
📄	white-rabbit.jpg

README.md

<footer>dinosaur.is</footer>

luddite.js

???

hey CampJS

i'm Mikey from Enspiral & Root Systems

slides are available at:

http://dinosaur.is/campjs-viii-ludditejs

???

second time presenting at a conference
i want to share what i am passionate about
- i might say negative things about some JavaScript patterns, but i use those patterns too
- i don't want to yuck your yum
i'll try to be upfront and honest, apologies in advance if i disguise any opinions as facts
in general everyone in the JavaScript community is doing a wonderful job, i appreciate your work

shout-out

???

when i was writing this talk a few days ago, deep in Imposter Syndrome, i realized...
- someone inspired my passion behind this talk without me realizing

Douglas Engelbart

augment human intellect

???

i take the Douglas Engelbart approach to developer experience
you may have heard of the Mother of all Demos, if not i highly recommend you check it out
he intended to boost collective intelligence to solve urgent global problems
Englebart's vision was that the power of technology came with inherent complexity
so priority is not ease of use but powerful human computer expression
let's evolve our JavaScript together to solve urgent global problems

references:

let's adventure

to the silly wonderland of luddite.js

???

an ambiguous utopia

Luddite?

the Luddites was a political movement against centralized automated technology.

???

many Luddites were skilled machine operators in the textile industry
they wanted machines to make high-quality goods, run by workers who had gone through an apprenticeship and got paid decent wages
they attacked centralized factories who used automated machines operated by unskilled labor
they used fictious characters to make their story ring
- see Ned Ludd, the made-up leader, who lived in Sherwood Forest

luddite.js?

luddite.js is a (made-up) meme for decentralized simple JavaScript.

decentralized userland ecosystems
simple patterns based on function signatures

???

not centralized core committees
not trendy libraries that lock you in
gonna lead you on a journey through the luddite way to do things
a study of functional JavaScript patterns that have evolved in userland

decentralized userland ecosystems

what if i told you...

that anyone can create a standard?

???

not everyone needs to agree with you
no corporate sponsorship necessary

what is a standard?

anything that enough people use is a "standard"

example: "standard style"

npm install --global standard

???

a standard is one opinion, shared my many
tc39 is a great team advancing the state of the art in JavaScript,
- but the standards produced by tc39 are only one of many possible JavaScript opinions
we all have the power to create our own JavaScript opinions
- no experience necessary!
what other standards can you think of?
- anything "best practice", maybe even within a small niche community

what if i told you...

that you only needed functions and objects?

???

no fancy syntax necessary
- less language clutter
how can we apply this pattern to the full stack?

what is a luddite.js standard?

a standard based on a function signature

example: Redux reducers

const reducer = (state, action) => nextState

???

what other standards based on function signatures can you think of?
- express / connect: (req, res, next)

why is this important?

easy to test
accessible for anyone to participate
no module lock-in

???

you can test the functions directly without using the module
you don't need anyone's approval to write a "function specification"
you can swap libraries that are compatible with the "function specification"

simple patterns based on function signatures

just a function

function fn (options) { return value }

const fn = (...args) => ({ [key]: value })

sync function signals

with a sync function, there are two possible signals:

value: return value
error: throw error

???

function fn (...args) { throw error }

try {
  fn(...args)
} catch (const err) {
  // handle error
}

modules

es modules

import thing from 'module'

export default thing

import { thing as thingy } from 'module'

export const thing = thingy

???

why new syntax?
- there's myths that es modules make possible something new
what is happening here?
- i find this can be confusing for beginners who don't understand the special syntax and complex implementation details
in the wild, export default breaks CommonJS code
- yes, i'm bitter about this, i've lost many hours debugging broken code, only to realize the module author published a patch version that broke the CommonJS exports

node modules

also known as "CommonJS"

const thing = require('module')

module.exports = thing

const { thing: thingy } = require('module')

module.exports = { thing: thingy }

???

it's just a function!
implementation details are simple:
- fs.readFileSync the module file
- wrap in closure to provide global variables like require, module, exports, global
- run code in JavaScript interpreter
- capture result of module.exports variable
when i started using Node.js from Python, require-as-a-function is what excited me the most
- so yes, i'm somewhat bitter that now JavaScript is adopting the same syntax as Python

dom elements

jsx

import React from 'react'
import classNames from 'classnames'

export default Todos

const Todos = ({ items }) => (
  <List>{items.map(item => (
    <Item item={item} />
  ))}</List>
)

const List = ({ children }) => (
  <div className='list'>{children}</div>
)

const Item = ({ item: { isActive, text } }) => {
  const className = classNames({
    item: true,
    active: isActive
  })
  return <div className={className}>{text}</div>
}

???

made by Facebook to make React easier to use
looks friendly on the surface, but underneath has non-obvious edge cases
- hides that JSX is actually React.createElement function calls
- "why can't i use if () { first } else { second }?
- can only use expressions, not statements

hyperscript

const h = require('react-hyperscript')
const classNames = require('classnames')

module.exports = Todos

const Todos = ({ items }) => (
  h(List, items.map(item =>
    h(Item, { item })
  ))
)

const List = ({ children }) => (
  h('div', { className: 'list' }, children)
)

const Item = ({ item: { isActive, text } }) => {
  const className = classNames({
    item: true,
    active: isActive
  })
  return h('div', { className }, text)
)

???

syntax can be confusing at first
React.createElement is basically a strict hyperscript

React.createElement

const h = require('react').createElement
const classNames = require('classnames')

module.exports = Todos

const Todos = ({ items }) => (
  h(List, null, items.map(item =>
    h(Item, { item })
  ))
)

const List = ({ children }) => (
  h('div', { className: 'list' }, children)
)

const Item = ({ item: { isActive, text } }) => {
  const className = classNames({
    item: true,
    active: isActive
  })
  return h('div', { className }, text)
)

eventual value

promise spec

const promise = new Promise((resolve, reject) => {
  // do stuff...
  resolve(value)
  // oh no!
  reject(error)
}

promise
  .then(value => console.log(value))
  .catch(err => console.error(value))

???

https://tc39.github.io/ecma262/#sec-promise-objects

TODO waterfall

parallel

module.exports = fetchCats

function fetchCats ({ cats }) {
  return Promise.all(cats.map(cat => {
    return fetch(cat)
  }))
})

continuable

a "continuable" is a function that takes a single argument, a node-style error-first callback

const continuable = (callback) => {
  // do stuff...
  callback(null, value)
  // oh no!
  callback(error)
}

continuable((err, value) => {
  if (err) console.error(err)
  else console.log(value)
})

???

a continuable is the callback version of a promise

can be passed around as an "eventual value", same as promises. but without the resolved, pending, rejected state machine complexity.

TODO waterfall

parallel

const request = require('request')
const parallel = require('run-parallel')

module.exports = fetchCats

function fetchCats ({ cats }) {
  return callback => parallel(cats.map(cat => {
    return callback => request(cat, callback)
  }), callback)
})

async errors

with a node-style error-first callback, there are three possible signals:

value: callback(null, value)
user error: callback(error)
programmer error: throw error

???

promise errors smush the user and programmer errors together
promises wrap all your handlers in a try / catch, so even if you have a different opinion about error handling, promises will force it's opinion on you
- yes, i'm bitter about this, i've lost many hours trying to figure out where my errors went

reactive values

es observables

https://tc39.github.io/proposal-observable/

???

too much detail to explain here

https://github.com/tc39/proposal-observable

observ-ables

reactive values using only functions!

thing() gets the value
thing.set(value) sets the value
thing((value) => { ... }) listens to the value

???

const { h, Struct, Value, when } = require('mutant')

const toggle = (state) => {
  state.set(!state())
}

const Activity = ({ activity: { isActive, text }) => (
  h('div', {
    style: {
      color: when(isActive, 'green', 'red')
    },
    events: {
      click: () => toggle(isActive)
    }
  }, text)
)

var activity = Struct({
  text: Value('give a talk'),
  isActive: Value(true)
})
var element = Activity({ activity })

document.body.appendChild(element)

???

mutant has observables for all composite data structures: arrays, sets, dictionaries, etc
updates in-place, no dom diff-ing!

values over time

node streams

https://nodejs.org/api/stream.html

???

whatwg streams

https://streams.spec.whatwg.org/

???

https://github.com/whatwg/streams

pull streams

async streams using only functions!

pull(source, through, sink)

composable partial pipelines
unbuffered by default
pipeline error propogation
source and sink back-pressure

???

pull streams could be its own talk, going to be a quick intro

source

function createSource (...args) {
  // a source function accepts
  //   - abort: a boolean whether to signal end
  //   - callback: where to send next signal
  return (abort, callback) => {
    if (abort || done) callback(true)
    else callback(null, value)
  }
}

???

look ma, just functions!
yes, we are using callbacks even for synchronous results
- much faster this way, no reason to delay til next tick

function values (array) {
  var i = 0
  return (abort, callback) => {
    if (abort || i === array.length) {
      callback(true)
    }
    else {
      callback(null, array[i++]
    }
  }
}

source usage

const values = require('pull-stream/sources/values')

const source = values([0, 1, 2, 3])

source(null, (err, value) {
  console.log('first value:', value)
})
// first value: 0

sink spec

function createSink (...args) {
  // a sink function accepts a source
  return (source) => {
    // reads a value from the source
    source(null, function next (err, value) {
      // handle the result
      if (err) return handleError(err)
      handleValue(value)

      // recursively call source again!
      source(null, next)
    })
  }
}

???

handleError might abort the source and call a done callback passed in through the args
handleValue might do something with each value

function log (source) {
  source(null, function next (err, data) {
    if (err) return console.log(err)
    console.log(data)
    // recursively call source again!
    source(null, next)
  })
}

with continuables:

function log (source) {
  return (callback) => {
    source(null, function next (err, data) {
      if (err) return callback(err)
      console.log(data)
      // recursively call source again!
      source(null, next)
    })
  }
}

sink usage

const values = require('pull-stream/sources/values')
const drain = require('pull-stream/sinks/drain')

const source = values([0, 1, 2, 3])
const log = drain(console.log)

log(source)
// 0
// 1
// 2
// 3

through spec

function createThrough (...args) {
  // a sink function: accept a source
  return (source) => {
    // but return another source!
    return (abort, callback) {
      // ...
    }
  }
}

???

function map (mapper) {
  // a sink function: accept a source
  return function (source) {
    // but return another source!
    return function (abort, callback) {
      source(abort, function (err, data) {
        // if the stream has ended, pass that on.
        if (err) callback(err)
        // apply a mapping to that data
        else callback(null, mapper(data))
      })
    }
  }
}

through usage

const values = require('pull-stream/sources/values')
const drain = require('pull-stream/sinks/drain')
const map = require('pull-stream/throughs/map')

const source = values([0, 1, 2, 3])
const log = drain(console.log)
const double = map(x => x * 2)

log(double(source))
// 0
// 2
// 4
// 6

compose pull streams

pull(source, through) // returns source

pull(through, sink) // returns sink

pull(source, sink) // runs to end

wild pull streams

ecosystem of modules: pull-stream.github.io

// parse a csv file
pull(
  File(filename),
  CSV(),
  pull.drain(console.log)
)

function CSV () {
  return pull(
    Split(), // defaults to '\n'
    pull.map(function (line) {
      return line.split(',')
    })
  )
}

???

obviously you don't want to re-implement simple streams from scratch all the time

pull stream errors

with a pull stream source callback, there are four possible signals:

value: callback(null, value)
user error: callback(error)
programmer error: throw error
complete: callback(true)

???

both the source and sink can signal back-pressure ("hey i'm busy") by not calling the respective callback

why should you be a JavaScript luddite?

better performance

software performance is less about gaining muscle, more about losing weight

???

code runs faster when it does less
if you don't use fancy syntax (jsx, etc), you don't need fancy build steps

easier to describe

specification is a function signature, not a complex state machine

???

clear inputs and outputs
small code blocks (or "snippets") can be deceiving
- leads to a positive first impression, until you use in production where the edge cases leak through the abstractions
- i find nothing more difficult than edge cases at scale caused by hiding complexity in our tools

path to mastery

learnable tools focused on power users

???

training wheels are great to get started and go around the blockS
yes promises are easier than callbacks, a beginner can start using with less learning, training, or practice
but when you want to go up a hill or go a long distance, you want a real bike
- this takes time to learn how to steer and balance on
how many hours to do we spend writing complex code, is the most intuitive abstraction best suited for our evolving understanding?
- here's one of many possible abstractions, but is not the end answer

stories

story: catstack

build a framework from scratch, alone

???

reinvent every wheel possible! the entire web stack.

https://github.com/root-systems/catstack

i did it, but it was unsustainable, unable to transfer context to team

learning:

yay, reinventing wheels for fun and learning

boo, the world on your shoulders

???

pros

no better way to learn how systems work than by building them from scratch
own your dependencies, don't consume them for granted
provide consistent flavoring across subsystems
marginally better than other libraries

cons

easy to become isolated
- if you aren't enough to become popular, you're alone
spreads you thin
- hard to work on what you can do best, because you have to spend limited resources on your marginally better stack
easy to rabbit hole
probably miss the long tail: i18n, accessibility, tests
always doing maintenance

revised: dogstack

choose your battles

???

focus on what you do best

delegates parts where you are only marginally better

http://dogstack.js.org/

story: patch ecosystem

bring-your-own-JavaScript potluck

???

build an app with others, bring your own JavaScript opinions

references:

http://patchwork.campjs.com

git projects

npm install -g git-ssb

learning: mad science works!

follow your passion

find others who share your passion

???

somebody should: if you see something that needs doing, it's your job to do
find ways to collaborate with active listening and empathy
mad science: find something worth doing, do it, publish, repeat

conclusion

so what

everyone has opinions.

this one is mine. =^.^=

???

as my Mom always says:

it's not about being right, it's about being successful

takaways

izs pants post: https://groups.google.com/forum/#!msg/nodejs/MWaivVTirPY/0pnRjKsggkIJ
- everyone has opinions, be aware of yours' and others'
- when you come over to someone's house, be polite and respect their opinions
don't force your opinions on others
- share what you're passionate about
- avoid persuading anyone that your way is better
the luddite.js way is just another opinion, not better or worse than yours

aids

eating your own dog food
mad science method
do-ocracy
marathon: keep a slow & steady pace one step at a time
if you see a job that needs doing, it's your job to do (do-ocrarcy)
too much sugar is bad for your health (simple interfaces)

blocks

cave method: try to design or implement the perfect system before sharing it
design by committee
sprint: hype, mania, and burn-out
waterfall design

all the "standards"

make up your own "standards"!

you have just as much a right to make the next JavaScript standard as anyone else.

???

at the end of the day, standards are just somebody's opinion.

questions?

thanks!

i appreciate the gift of your attention. ♥

???

references

luddite.js apps

Built with git-ssb-web

dinoworm 🐛 / campjs-viii-ludditejs