Philosophy

[craigspaeth]

Taking notes on some ideas to reference when making decisions on picking tools and designing APIs...

• foo.use(() =>) can be a common way to mixin functionality
• foo.on('bar baz', () =>) can be a way to hook into lifecycle/events/scoped-things
• Arrow functions all around, avoiding classes and this
• Async/await over callbacks/generators/plain-promises
• Middleware as a common composition pattern
• Standard format linted
• Stage 4 approved, Node-first universal, JS (e.g. Avoiding transpiled additions like JSX, flow, webpack loaders or browserify transforms)
• Solve for 80% of use cases with obvious escape hatches for the other 20%
• minimal > proper
• obvious > pure
• pragmatic > the right way
• composition > inheritence
• fun > jargon
• procedural/functionalish > OO
• explict > implicit
• wrapping modules > convention > configuration
• stand on shoulders of tall people > re-invent the wheel

Some articles that feels aligned in some ways:

• http://www.christianalfoni.com/articles/2016_09_11_The-case-for-function-tree
• http://www.christianalfoni.com/articles/2015_11_16_Flux-vs-Single-State-Tree
• https://github.com/yoshuawuyts/choo#philosophy
• http://staltz.com/some-problems-with-react-redux.html
• https://medium.com/javascript-scene/the-two-pillars-of-javascript-ee6f3281e7f3
• https://www.infoq.com/presentations/Simple-Made-Easy