This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
Latency Comparison Numbers (~2012) | |
---------------------------------- | |
L1 cache reference 0.5 ns | |
Branch mispredict 5 ns | |
L2 cache reference 7 ns 14x L1 cache | |
Mutex lock/unlock 25 ns | |
Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
Compress 1K bytes with Zippy 3,000 ns 3 us | |
Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
# 0 is too far from ` ;) | |
set -g base-index 1 | |
# Automatically set window title | |
set-window-option -g automatic-rename on | |
set-option -g set-titles on | |
#set -g default-terminal screen-256color | |
set -g status-keys vi | |
set -g history-limit 10000 |
This launchd script will ensure that your Docker environment on your Mac will have 10.254.254.254
as an alias on your loopback device (127.0.0.1). The command being run is ifconfig lo0 alias 10.254.254.254
.
Once your machine has a well known IP address, your PHP container will then be able to connect to it, specifically XDebug can connect to it at the configured xdebug.remote_host
.
Copy/Paste the following in terminal with sudo (must be root as the target directory is owned by root)...
# Instruction + template repo: https://github.com/FedericoPonzi/rust-ci | |
# Search and replace <YOUR_BINARY_NAME> with your binary name. | |
name: CI | |
on: | |
pull_request: | |
push: | |
branches: | |
- master | |
tags: |
settings put global captive_portal_mode 1 | |
settings put global captive_portal_use_https 1 | |
settings put global captive_portal_http_url http://connect.rom.miui.com/generate_204 | |
settings put global captive_portal_https_url https://connect.rom.miui.com/generate_204 | |
settings put global captive_portal_fallback_url http://captive.v2ex.co/generate_204 | |
settings put global captive_portal_other_fallback_urls http://www.google.cn/generate_204 |
/* | |
I've wrapped Makoto Matsumoto and Takuji Nishimura's code in a namespace | |
so it's better encapsulated. Now you can have multiple random number generators | |
and they won't stomp all over eachother's state. | |
If you want to use this as a substitute for Math.random(), use the random() | |
method like so: | |
var m = new MersenneTwister(); |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying