Zirak

//http://www.w3.org/TR/2011/WD-page-visibility-20110602/
(function () {
	"use strict";

	//no need to shim if it's already there
	if ( 'hidden' in document && 'onvisibilitychange' in document ) {
		return;
	}

	//fail silently if the browser sux

domenic

// This event emitter emits events, but reserves the right to publish events to
// for its creator. It uses a WeakMap for true encapsulation.

const eesToEventMaps = new WeakMap();

export default class EventEmitter {
    constructor(publisher) {
        const eventMap = Object.create(null);
        eesToEventMaps.set(this, eventMap);

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.

---

jsocol

Great resources on Queues

• Queue Everything and Delight Everyone
• Lessons Learned with Distributed Systems at Bitly
• NSQ
• How TodaysMeet Works
• Visualizing the 2015 SotU on TodaysMeet
• this talk

ajfisher

spion

Node streams - a fractal of weird design

and a potential refactor that could fix that

This is a list of issues and confusions I've encountered with node streams, and things I wish were designed and implemented differently. If promise-streams is ever going to change to a design that doesn't build on top of node streams, this would be a list of mistakes to avoid

1. enc parameter - Why is encoding always passed together with the data? It should be a separate concern. It doesn't even make sense in objectMode
2. eventemitter base - This encourages a lot of random events to be "attached" by other authors which doesn't work. Best to have an uniform (typed) interface so that everyone knows what to expect.
3. relying on nextTick etc for execution order - This is very unreliable and causes all sorts of unpredictable rules for implementers which are not documented anywhere. When you attach listeners determines what will happen.
4. no error propagation - we need the

squarism

"You have time you can control and time you can't,
you can't devote all of the time you can control to
new features otherwise the that time shrinks to 0."
-- reconbot


                ┌─────────                 
                │   ┌────                  
                │   │                      
                │   │   ▲