laduke

//    maybeToFuture :: a -> Maybe b -> Future a b
const maybeToFuture = S.curry2((x, maybe) =>
  S.maybe(Future.reject(x), Future.of, maybe)
);

//also 
/*
Aldwin Vlasblom @Avaq Aug 14 05:12
I generally have two strategies for dealing with a Future(Just(x)):
Using maybeToFuture. @davidchambers just posted an implementation. I use this when Nothing represents an actual error in the code (one that can only be recovered from by my generic error recovery procedure, which usually reports the error and crashes the process).

laduke

(defun aj-javascript/post-init-mmm-mode ()
  (with-eval-after-load 'rjsx-mode
    (mmm-add-classes '((yo
                        :submode web-mode
                        :front "html`"
                        :back "`"
                        :face mmm-declaration-submode-face)))
    (mmm-add-mode-ext-class 'rjsx-mode nil 'yo)
    (setq mmm-parse-when-idle 't)
    ))

laduke

var daggy = require('daggy')

const Machine = daggy.taggedSum('Timer', {
  Yellow: [],
  Green: [],
  Red: []
})

Machine.prototype.timer =
  function () {

laduke

var http = require('http')
var { html, title, head, body, div } = require('hyperaxe')

var page = html(
  head(title('hi')),
  body(
    div({ id: 'app' })
  )
).outerHTML

laduke

Find your auth token

the authtoken.secret file

• On Mac this is in "/Library/Application Support/ZeroTier/One". also, the installer copies it to ~/Library/Application
  Support/ZeroTier/One
• Windows this is usually in "\ProgramData\ZeroTier\One". also, the installer copies it somewhere local to the installing user... I

laduke

Set up a controller with curl

1 Find your auth token

the authtoken.secret file

• On Mac this is in “/Library/Application Support/ZeroTier/One”. also, the installer copies it to ~/Library/Application\ Support/ZeroTier/One
• Windows this is usually in “\ProgramData\ZeroTier\One”. also, the installer copies it somewhere local to the installing user… I forget
• On Linux this is usually in “/var/lib/zerotier-one”.

laduke

function h(tag, as, xs) {
  var attrs = Object.entries(as).map(([k, v]) => ` ${k}="${v}"`);

  return `<${tag}${attrs}>${xs.join("")}</${tag}>`;
}

console.log(
  h("div", { id: "foo" }, [
    h("p", { class: "big" }, ["hi", h("p", {}, ["3"])]),
    h("p", {}, ["bye"])

laduke

Testing out a test thing

• https://github.com/hyperdivision/vhs-tape
• https://github.com/hyperdivision/hui
• https://github.com/davidkpiano/xstate/tree/master/packages/xstate-test
• https://github.com/davidkpiano/xstate

laduke

const myMachine = Machine({
  type: 'parallel',
  context: {},

  states: {
    hi: {
      initial: 'no',
      states: {
        yes: {},
        no: { on: { CLICK_ME: 'yes' } }

laduke

Typically, you use zerotier-cli to join and leave networks, but you can also write files to the filesystem to do this.

The networks.d subdirectory of the ZeroTier working directory keeps track of which networks are joined and their settings.

The ZeroTier working directory can be found...

• On Windows: \ProgramData\ZeroTier\One
• On Mac: /Library/Application Support/ZeroTier/One
• On Linux: /var/lib/zerotier-one