Forked from Captain Anonymous's Pen QjGzqw.
Forked from Captain Anonymous's Pen QjGzqw.
A Pen by Christian Talmo on CodePen.
Forked from Captain Anonymous's Pen QjGzqw.
Forked from Captain Anonymous's Pen QjGzqw.
A Pen by Christian Talmo on CodePen.
{ | |
"Working Directory" : "\/Users\/mollie", | |
"Prompt Before Closing 2" : 0, | |
"Selected Text Color" : { | |
"Green Component" : 0.0921427, | |
"Blue Component" : 0.09770776, | |
"Red Component" : 0.0869376 | |
}, | |
"Rows" : 25, | |
"Ansi 11 Color" : { |
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
<plist version="1.0"> | |
<dict> | |
<key>Ansi 0 Color</key> | |
<dict> | |
<key>Alpha Component</key> | |
<real>1</real> | |
<key>Blue Component</key> | |
<real>0.176470547914505</real> |
There's been a strange explosion in misinformation about browserify recently, particularly in comparisons to webpack.
Generally speaking, most of this confusion stems from how webpack is more willing to pull features into its core to ease discoverability while browserify is more likely to push features out to userland instead.
I think that longer-term, separability has more benefits from a maintenance and
#!/bin/bash | |
# Usage: ./convert.sh file | |
for arg; do | |
echo "" | |
echo "arg: $arg" | |
inputFile=$arg | |
outputFile="$inputFile.output.mp4" |
#!/bin/bash | |
EXECUTE=0 | |
VERBOSITY=0 | |
function log { | |
if [[ $VERBOSITY -ge 1 ]]; then | |
echo "$@" | |
fi | |
} |
import { ExchangeService, ExchangeVersion, ExchangeCredentials, Uri, DateTime, CalendarView, WellKnownFolderName, EwsLogging } from "ews-javascript-api"; | |
import credentials = require("./credentials"); //for username and password | |
EwsLogging.DebugLogEnabled = false; | |
var service = new ExchangeService(ExchangeVersion.Exchange2010); | |
service.Credentials = new ExchangeCredentials(credentials.userName, credentials.password); | |
service.Url = new Uri("https://outlook.office365.com/Ews/Exchange.asmx"); | |
var view = new CalendarView(DateTime.Now.Add(-1, "week"), DateTime.Now); // appointments in last one week. |
sourcefile=$1 | |
destfile=$2 | |
# Overly simple validation | |
if [ ! -e "$sourcefile" ]; then | |
echo 'Please provide an existing input file.' | |
exit | |
fi | |
if [ "$destfile" == "" ]; then |
var net = require('net'); | |
var util = require('util'); | |
var Writable = require('stream').Writable; | |
/** | |
* Pretends to consume the data written to it. In reality, it just eats data | |
* really slowly. | |
* | |
* @constructor | |
* @extends Writable |
A quick overview of the node.js streams interface with basic examples.
This is based on @brycebaril's presentation, Node.js Streams2 Demystified
Streams are a first-class construct in Node.js for handling data.
Think of them as as lazy evaluation applied to data.