Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules.
Source tweet: https://twitter.com/rauchg/status/712799807073419264
const leftPad = await requireFromTwitter('712799807073419264');
#!/bin/bash | |
# | |
# Credits to fuckbecauseican5 from https://www.reddit.com/r/hackintosh/comments/4s561a/macos_sierra_16a238m_install_success_and_guide/ | |
# Adapted to work with the official image available into Mac App Store | |
# | |
# Enjoy! | |
hdiutil attach /Applications/Install\ macOS\ Sierra.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app | |
hdiutil create -o /tmp/Sierra.cdr -size 7316m -layout SPUD -fs HFS+J | |
hdiutil attach /tmp/Sierra.cdr.dmg -noverify -nobrowse -mountpoint /Volumes/install_build |
Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules.
Source tweet: https://twitter.com/rauchg/status/712799807073419264
const leftPad = await requireFromTwitter('712799807073419264');
Create a template service file at /etc/systemd/system/[email protected]
. The template parameter will correspond to the name
of target host:
[Unit]
Description=Setup a secure tunnel to %I
After=network.target
There is a huge body of valid and yet faked or non-existing things you can use freely e.g. for testing purposes: | |
* The "Null Island" being a geographical convenience, non-existing island: "Null Island is a fictional island in the Gulf of Guinea | |
added to the Natural Earth public domain map dataset, located where the equator crosses the prime meridian, at coordinates 0°N 0°E." | |
see details: https://en.m.wikipedia.org/wiki/Null_Island - it even has a fake travel website :) | |
http://www.nullisland.com/travel.html | |
* On TV, you see the recurring fake phone number: https://en.wikipedia.org/wiki/Fictitious_telephone_number | |
#!/bin/bash | |
PLIST=platforms/ios/*/*-Info.plist | |
cat << EOF | | |
Add :NSAppTransportSecurity dict | |
Add :NSAppTransportSecurity:NSAllowsArbitraryLoads bool YES | |
EOF | |
while read line | |
do |
This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.
In that post I talked about 3 main reasons for moving from require.js to webpack:
Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.
#!/bin/sh | |
if [ "$(id -u)" != "0" ]; then | |
echo "Sorry, you are not root." | |
exit 1 | |
fi | |
if !(type pcp 2>/dev/null;) then | |
yum -y install git bison flex gcc-c++ perl-Tk-devel libmicrohttpd-devel | |
git clone git://git.pcp.io/pcp |
Liquid Fill Gauge v1.1 - 7/14/2015
Changes:
Configurable features include:
var gulp = require('gulp'); | |
var browserify = require('browserify'); | |
var babelify = require('babelify'); | |
var del = require('del'); | |
var source = require('vinyl-source-stream'); | |
var _ = require('lodash'); | |
var extReplace = require('gulp-ext-replace'); | |
var less = require('gulp-less'); | |
var gulpMerge = require('merge-stream'); | |
var ngTemplates = require('gulp-ng-templates'); |
Magic numbers are the first bits of a file which uniquely identify the type of file. This makes programming easier because complicated file structures need not be searched in order to identify the file type.
For example, a jpeg file starts with ffd8 ffe0 0010 4a46 4946 0001 0101 0047 ......JFIF.....G ffd8 shows that it's a JPEG file, and ffe0 identify a JFIF type structure. There is an ascii encoding of "JFIF" which comes after a length code, but that is not necessary in order to identify the file. The first 4 bytes do that uniquely.
This gives an ongoing list of file-type magic numbers.