aenain

/*
This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or
distribute this software, either in source code form or as a compiled
binary, for any purpose, commercial or non-commercial, and by any
means.

In jurisdictions that recognize copyright laws, the author or authors
of this software dedicate any and all copyright interest in the

fijiwebdesign

function testConnection() {
	var url = location.href.match(/^https?\:/i) ? '/' : 'https://google.com'
	var rand =  parseInt(Math.ceil(Math.random()*Math.pow(10, 14))).toString(16)
	var retry = ms => setTimeout(() => testConnection(), ms || 5000)
	var notify = msg => document.body.innerHTML = `<h1 style="font-size:300%;position:fixed;top:40%;width:100%;text-align:center;">${msg}</h1>`
	var handleResp = (err, msg) => {
		console.log(err, new Date, msg)
        notify(msg)
		retry()
    }

reggi

http://blog.gmane.org/gmane.comp.security.openwall.john.user/month=20140601

error: No MPI compiler found john the ripper

phusion/passenger#1630 (comment)

paulirish

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

CMCDragonkai

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on

rbuckton

Summary

One issue introduced by decorators is that any attempt to use them on a function declaration would either necessitate a TDZ for the declaration, or would need to be an error. This limits the usefullness of decorators.

Another issue is that many use cases for annotations need a coherent runtime API that allows for imperative reflection for annotations of an object, its members, or the parameters of a function.

This document describes two parts to a solution for unifying decorators and annotations:

1. Marking decorators as "early" with the @decorator decorator.
2. Extending the Reflect API with a comprehensive set of functions for reflecting and managing metadata.

trevnorris

native-stream.js uses the reference implementation, compiled with babel to run
on latest io.js.

stream-bluebird.js is exactly the same as native-stream.js except it uses the
latest bluebird Promise implementation.

node-stream.js uses the node stream implementation and forced to be async by
using process.nextTick() (which is functionally equivalent to the microtask
processor)

calvinmetcalf

var Promise = global.Promise || require('lie');
function noop(){}
function typeIsObject(x) {
  return (typeof x === 'object' && x !== null) || typeof x === 'function';
}
function ExclusiveStreamReader () {
  throw new Error('not implimented');
}
function ReadableStream(opts) {
  var start = opts.start || noop;

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.

---