bsharper

# If you run this as a script it should patch and compile BPG for you
wget http://bellard.org/bpg/libbpg-0.9.tar.gz
tar xvzf libbpg-0.9.tar.gz
cd libbpg-0.9
wget https://gist.githubusercontent.com/bsharper/dd517547f6e1bcabf6be/raw/d125ab609e07e4fd624137543d36eb48bcaab91b/bpg_osx.patch
patch -p1 < bpg_osx.patch
# Output should be:
#   patching file Makefile
#   patching file libavutil/mem.c
# If you see something like "patch unexpectedly ends in middle of line" it should still work

barneycarroll

var animating = false;

// Define an animator consisting of optional incoming and outgoing animations. 
// alwaysAnimate is false unless specified as true: false means an incoming animation will only trigger if an outgoing animation is also in progress.
// forcing dontClone to true means the outward animation will use the original element rather than a clone. This could improve performance by recycling elements, but can lead to trouble: clones have the advantage of being stripped of all event listeners.
function animator( incoming, outgoing, alwaysAnimate, dontClone ){
	// The resulting animator can be applied to any number of components
	return function animate( x, y, z ){
		var config;
		var parent;

StephanHoyer

'use strict';

var m = require('mithril');
var extend = require('lodash').extend;
var setFocus = require('../util/viewhelper').setFocus;
var keymage = require('keymage');

function noop(){}

function addClass(el, className) {

joyrexus

Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.

“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”

---

Matt Bridges' answer in full:

The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing

avesus

xset r rate 170 77 setxkbmap -layout "us,ru" -option "grp:caps_toggle" -option "grp_led:scroll" -option "compose:ralt"

pelonpelon

function state (namespace) {
  if (!namespace) return internalState[internalState.length - 1]
  internalState.push([namespace, options])
  m.redirect(namespace, options)
}

function goto (namespace, options) {
  return function (e) {
    e.preventDefault()
    e.stopPropagation()

Naddiseo

/* global require, module */
var isString = require('lodash/lang/isString');

var htmlTags = (
	'^(html|base|head|link|meta|style|title|address|article|' +
	'body|footer|header|h[1-6]|hgroup|nav|section|dd|div|dl|dt|' +
	'figcaption|figure|hr|li|main|ol|p|pre|ul|a|abbr|b|bdi|bdo|br|' +
	'cite|code|data|dfn|em|i|kbd|mark|q|rp|rt|rtc|ruby|s|samp|small|span|strong|sub|' +
	'time|u|var|wbr|area|audio|img|map|track|video|embed|iframe|object|param|source|' +
	'canvas|noscript|script|del|ins|caption|col|colgroup|table|tbody|td|tfoot|th|thead|tr|' +

MattMcFarland

Table of Contents:

• Why FLUX?
• About this Guide
• Library Dependencies
• Directory Structure
• store.js
• constants.js
• dispatcher.js
• actions.js
• app.js

jakub-g

Beware of <script async defer> blocking HTML "load" event

2015.10.07 t

On the importance of simulated latency testing, and bulletproofing your page from the third-party JS load failures

TL;DR

mattatz

// BitwiseOperations.glsl

const int BIT_COUNT = 8;

int modi(int x, int y) {
    return x - y * (x / y);
}

int or(int a, int b) {
    int result = 0;