Skip to content

Instantly share code, notes, and snippets.

@lifthrasiir
lifthrasiir / UserScript.html
Created July 22, 2012 13:47
UserScript: a forgotten programming language from the hell (2003)
<html>
<head>
<title>UserScript version 0.2.3</title>
<link rel="stylesheet" href="common.css" type="text/css" />
</head>
<body>
<h1>UserScript 레퍼런스 <small>UserScript Reference</small></h1>
@dergachev
dergachev / GIF-Screencast-OSX.md
Last active July 17, 2024 14:20
OS X Screencast to animated GIF

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Screencapture GIF

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

@khris
khris / conf.py.dist
Created May 11, 2014 13:40
Simple Twitter bot
OAUTH_TOKEN = '<YOUR ACCESS TOKEN>'
OAUTH_SECRET = '<YOUR ACCESS TOKEN SECRET>'
CONSUMER_KEY = '<YOUR API KEY>'
CONSUMER_SECRET = '<YOUR API SECRET>'
# seconds
INTERVAL = 30
@lifthrasiir
lifthrasiir / no-box.md
Last active June 27, 2017 08:46
Idiomatic Rust: Yes I'm really trying to write something similar

No Box<T>

tl;dr: Avoid Box<T> in general.

Actually, this rule is so important that the Rust Pointer Guide explicitly says the same. Therefore without a further ado, you should avoid Box<T> except for these three cases:

  1. When you absolutely need a trait object (Box<Trait>). But review carefully to see if it is indeed absolutely needed; you may try to generalize things too far, for example.

  2. When you have a recursive data structure. This may be mandatory when you have an inherently recursive data (e.g. scene graph), but it may also be a sign of the premature optimization. Again, review carefully to see if you need to write a separate data structure yourself, and use the collection crate if possible.

@ageis
ageis / openpgp-card-guide.md
Last active June 14, 2024 07:10
Quick GPG Smartcard Guide