othiym23

[fit] constantly losing stuff

lessons learned developing and using continuation-local-storage in Node

Forrest L Norvell, npm, Inc.

othiym23 on npm / GitHub / Twitter

^ code-heavy talk that focuses on Node; some interesting pieces for the front end towards the end

---

othiym23

const assert = require('assert')

module.exports = solve

const RIGHT = Symbol('RIGHT')
const UP = Symbol('UP')
const LEFT = Symbol('LEFT')
const DOWN = Symbol('DOWN')

function generate (turn) {

othiym23

arm64 build notes

Google really wants anything arm-related to be cross-compiled instead of built on the ARM device. A pity, because @groundwater found a really awesome and cheap service that rents out 96-core arm64 servers.

The current Electron build infrastructure is designed to make it quick for end-user developers to put together their apps. Many pieces that are built at the same time are packaged separately,

othiym23

Eclipse boxes.todo

• 03: Late Ozu @done(2017-02-16)
  • 早春 / Early Spring (1956) @done(2017-02-10)
  • 東京暮色 / Tokyo Twilight (1957) @done(2017-02-13)
  • 彼岸花 / Equinox Flower (1958) @done(2017-02-14)
  • 秋日和 / Late Autumn (1960) @done(2017-02-15)
  • 小早川家の秋 / The End of Summer (1961) @done(2017-02-16)
• 09: The Delirious Fictions of William Klein @done(2017-02-21)
  • Who Are You, Polly Magoo? (1966) @done(2017-02-17)
  • Mr. Freedom (1969) @done(2017-02-20)

othiym23

How to figure out what the fuck is going on without social media.

Sourced breaking news

• The Washington Post
• The Guardian
• ProPublica
• The New Yorker
• The Economist
• The New York Times, I guess

othiym23

President: Hillary (ugh)
Senator: nope
Representative, D12: nope / Preston Picus
State Senate: Jane Kim
Assembly, District 19: nope
Superior Court Judge, Office No. 7: Victor Hwang
Board of Education: Stevon Cook, Matt Haney, Mark Sanchez
Community College Board: Rafael Mandelman, Tom Temprano, Shanell Williams
BART Board, D7: Lateefah Simon
BART Board, D9: Bevan Dufty (ugh ugh)

othiym23

team goal, end of 2016Q2:

• remove blockers to adoption of npm@3
• try to get Node lts cut over to npm@3 exclusively

current problem:

• things are moving very slowly

takeaway:

• not a lot of the rest of the road map is going to happen in 2016

othiym23

bauchelain% n t

> eliminate-5082@1.0.0 test /Users/ogd/Documents/projects/test-sandwiches/eliminate-5082
> node stress.js

TAP version 13
# run 1
not ok  1 - error: tap returned 1
1..1
/Users/ogd/Documents/projects/test-sandwiches/eliminate-5082/test.js .. 12/13

othiym23

autoscale: true

[fit] the npm cache

[fit] the part of the animal nobody likes

---

what is it for?

othiym23

178089 verbose url raw core-util-is
178090 verbose url resolving [ 'https://registry.npmjs.org/', './core-util-is' ]
178091 verbose url resolved https://registry.npmjs.org/core-util-is
178092 info trying registry request attempt 1 at 11:37:13
178093 verbose etag "75RK9UUWAHLYO40UZKLLOJ8YF"
178094 http GET https://registry.npmjs.org/core-util-is
178095 verbose cache add [ 'error-ex@^1.2.0', null ]
178096 verbose cache add name=undefined spec="error-ex@^1.2.0" args=["error-ex@^1.2.0",null]
178097 verbose parsed url { protocol: null,
178097 verbose parsed url   slashes: null,