danielfilho

#BrazilJS 2014

Talks: slides & Links

Day	Talk	Speaker	Links
1	Why ServiceWorker may be the next big thing	Renato Mangini	interview · slides · video
1	Frontend at Scale - The Tumblr Story	Chris Miller	interview · slides · video
1	Intro to GFX: Raw WebGL	Nick Desaulniers	interview · slides · video

fdaciuk

/* jslint browser: true, jquery: true, devel: true*/

/*
  Dependencies: Tumblr.Flags

  Tumblr.Utils.exceptions will automatically log window.onerror.

  DO NOT write code like this. This is written to handle weird cases
  where normal code should probably just fail.
*/

stephenparish

Commit Message Conventions

These rules are adopted from the AngularJS commit conventions.

• Goals
• Generating CHANGELOG.md
  • Recognizing unimportant commits
  • Provide more information when browsing the history
• Format of the commit message
• Subject line

john2x

Clojure Destructuring Tutorial and Cheat Sheet

(Related blog post)

Simply put, destructuring in Clojure is a way extract values from a datastructure and bind them to symbols, without having to explicitly traverse the datstructure. It allows for elegant and concise Clojure code.

Vectors and Sequences

evancz

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

lygaret

define(function(require) {
    var React = require('react');

    var paramRegex  = /__(\d)+/;
    var parser      = new DOMParser();
    var errorDoc    = parser.parseFromString('INVALID', 'text/xml');
    var errorNs     = errorDoc.getElementsByTagName("parsererror")[0].namespaceURI;

    // turns the array of string parts into a DOM
    // throws if the result is an invalid XML document.

timrwood

manager	dist	manifest	export	ignore	include	entry
npm	npm	package.json	cjs	.npmignore		#main
bower	git	bower.json	umd	#ignore		#main
component	git	component.json	umd		#files	#main
spm	git	package.json#spm	umd	.spmignore	#output	#main
packagist	git	composer.json	umd
ender	npm	package.json	cjs	.npmignore		#ender
dojo	???	package.json#dojoBuild	umd			#dojoBuild
jspm	npm/git	package.json#jspm	any	#ignore	#files	#main

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

scottjehl

I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.

TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

---

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).

Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

remy

'use strict';
var timer = setTimeout(function () {
  console.log('I AM ALIVE!');
}, 1000);

timer.unref();

console.log('Going to lay down now. Right now.');