howiemnet

// NOTE: ignore the .cpp extension on the filename - this is VEX
//       but I couldn't find a gist-friendly way to syntax-hilight it
//       ¯\_(ツ)_/¯
//
// h's magic adaptive point resizer for optimal
// rendering of tiny points/particles/wires
//
// 1/2/2018 [email protected]
// CC-0 - use and abuse

florentchauveau

-- Redis script to implement a leaky bucket
-- see https://medium.com/callr-techblog/rate-limiting-for-distributed-systems-with-redis-and-lua-eeea745cb260
-- (c) Florent CHAUVEAU <[email protected]>

local ts  = tonumber(ARGV[1])
local cps = tonumber(ARGV[2])
local key = KEYS[1]

-- remove tokens < min (older than now() -1s)
local min = ts -1

florentchauveau

-- Redis script to get the size of a token bucket
-- see https://medium.com/callr-techblog/rate-limiting-for-distributed-systems-with-redis-and-lua-eeea745cb260
-- (c) Florent CHAUVEAU <[email protected]>

local ts  = tonumber(ARGV[1])
local key = KEYS[1]

-- remove tokens < min (older than now() -1s)
local min = ts -1

florentchauveau

-- Redis script to add an event to a token bucket
-- see https://medium.com/callr-techblog/rate-limiting-for-distributed-systems-with-redis-and-lua-eeea745cb260
-- (c) Florent CHAUVEAU <[email protected]>

local ts = tonumber(ARGV[1])

-- set the token bucket to 1 second (rolling)
local min = ts -1

-- iterate overs keys

warrenm

#include <metal_stdlib>
using namespace metal;

struct VertexIn {
    float2 position [[attribute(0)]]; // varies per-vertex
    float4 color    [[attribute(1)]]; // varies per-instance
    float3 center   [[attribute(2)]]; // varies per-instance
    float  radius   [[attribute(3)]]; // varies per-instance
};

vvvvalvalval

;; # EMULATING DATOMIC EXCISION VIA MANUAL DATA MIGRATION


;; *************************************
;; ## Introduction
;; *************************************

;; This Gist demonstrates a generic way to migrate an entire Datomic database
;; from an existing 'Origin Connection' to a clean 'Destination Connection',
;; while getting rid of some undesirable data and otherwise preserving history.

turbo

global
    log 127.0.0.1 local0 notice
    maxconn 4096
    user haproxy
    group haproxy
    ssl-server-verify none

defaults
    log     global
    mode    http

steven2358

FFmpeg cheat sheet

A list of useful commands for the FFmpeg command line tool.

Download FFmpeg: https://www.ffmpeg.org/download.html

Full documentation: https://www.ffmpeg.org/ffmpeg.html

Basic conversion

technomancy

To me, "require-and-automatically-visible" is violating the beauty of namespace. But, maybe I felt this way because I don't understand Clojure's registry or how require works.

I thought about this more, and I think I have a better understanding of why this feels strange. Clojure has one thing called "namespaces" which are clojure.lang.Namespace objects created by the ns macro. Functionally speaking they are a storage location which mostly just contain vars and references to vars in other namespaces. They are used for code organization: specifically for organizing vars and occasionally Java classes and interfaces.

Clojure also has a completely different thing called "namespaces" which are prefixes that get attached to keywords and symbols. These can interact with ns namespaces thru the reader in a handful of ways (for instance, ::double-colon keywords and symbols inside backtick forms are resolved according to the current clojure.lang.Namespace) but for the most part should be considered a di

GuilloOme

(function() {
    'use strict';

    // keep track of all the opened tab
    let tabs = {};

    // Get all existing tabs
    chrome.tabs.query({}, function(results) {
        results.forEach(function(tab) {
            tabs[tab.id] = tab;