Bananattack

import "ram";
import "entity";
import "directions";
import "random";

namespace ai_wander {
    const direction_wait_base : [u8] = [60];
    const direction_wait_random : [u8] = [60];
    const wander_speed_lo : [u8] = [128];
    const wander_speed_hi : [u8] = [0];

helmutschneider

import * as ts from 'typescript'
import { Rules, RuleWalker, RuleFailure } from 'tslint'

function find<T>(collection: T[], predicate: (it: T) => boolean): T | null {
    for (const item of collection) {
        if (predicate(item)) {
            return item
        }
    }
    return null

Yonezpt

// ==UserScript==
// @version  1.0.2
// @name     Removes the autoplay up next feature
// @match    *://www.youtube.com/*
// @run-at   document-start
// @grant    none
// @noframes
// ==/UserScript==
(function () {
    'use strict';

paniq

Below I collected relevant links and papers more or less pertaining to the subject of tetrahedral meshes. 
It's an ever-growing list.

------------------------------
Relevant links: 

http://en.wikipedia.org/wiki/Types_of_mesh
http://en.wikipedia.org/wiki/Tetrahedron
http://en.wikipedia.org/wiki/Simplicial_complex

elib

float sidepercent = 6;

//10-20 -> amazing horizontals
//100 -> painterly
float initialChanceOfChunkGrab = 15;
float chanceOfChunkGrab;

float chanceOfChunkGrabChange = 10;

mcpherrinm

I want to write Rust code on my computer (x86_64, Ubuntu 14.04) and produce arm executables. I found hints on the internet, but not a concise set of instructions on what to do. So I wrote them down exactly:

apt-get install g++-arm-linux-gnueabihf
git clone https://github.com/mozilla/rust.git
mkdir rust/build-cross
cd rust/build-cross
../configure --target=arm-unknown-linux-gnueabihf --prefix=$HOME/local/rust-cross
make -j8 && make install

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

StefanoRausch

[

    { "keys" : [ "alt+1" ], "command" : "focus_group", "args" : { "group" : 0 } },

    { "keys" : [ "alt+2" ], "command" : "focus_group", "args" : { "group" : 1 } },

    {   // workspace left
        "keys" : [ "ctrl+alt+super+left" ],
        "command" : "run_multiple_commands",
        "args" : {

jakevsrobots

Shader "VertexInputSimple" {
  Properties {
    _SoundWavePosition ("Sound Wave Position", Vector) = (0,0,0,0)
    _SoundWaveRange ("Sound Wave Range", Float) = 2.0
    _SoundWaveWidth ("Sound Wave Width", Float) = 0.1

    _MainTex ("Texture", 2D) = "white" {}
  }

  

henkboom

using UnityEngine;
using System.Collections.Generic;

// Data that expires on scene close.
// Pretty much a hack, there must be a better way!
class SceneData<T> where T : class
{
    GameObject go;
    T data;