Jason Scott js1972

## streams-tutorial.md

      
              1 file
            
          
              23 forks
            
          
              6 comments
            
          
              184 stars
            
          
                djspiewak
                / streams-tutorial.md
            
            
              Created
              March 22, 2015 19:55
            
              
                Introduction to scalaz-stream
              
          
    Introduction to scalaz-stream

Every application ever written can be viewed as some sort of transformation on data.  Data can come from different sources, such as a network or a file or user input or the Large Hadron Collider.  It can come from many sources all at once to be merged and aggregated in interesting ways, and it can be produced into many different output sinks, such as a network or files or graphical user interfaces.  You might produce your output all at once, as a big data dump at the end of the world (right before your program shuts down), or you might produce it more incrementally.  Every application fits into this model.
The scalaz-stream project is an attempt to make it easy to construct, test and scale programs that fit within this model (which is to say, everything). It does this by providing an abstraction around a "stream" of data, which is really just this notion of some number of data being sequentially pulled out of some unspecified data source. On top of this abstraction, sca

  
## appcache-tooling.md

      
              1 file
            
          
              1 fork
            
          
              2 comments
            
          
              10 stars
            
          
                addyosmani
                / appcache-tooling.md
            
            
              Last active
              August 29, 2015 14:05
            
              
                AppCache manifest generation tooling
              
          
Tools that read through a directory, stream or tree and create an Application Cache manifest for you.

AppCache is still a douche but luckily there are tools available to take the pain out of generating your initial manifest files:

Grunt: grunt-manifest is currently the de facto option, but the project lead is looking for a new maintainer. In light of that grunt-appcache is an alternative in case you're looking for more active support.
Gulp: gulp-manifest is inspired by grunt-manifest and has a similar set of options.
Broccoli: broccoli-manifest brings manifest file compilation based on trees.

Do review what is generated. As with any automation tooling, be careful that what is being generated is what you actually intend on being cached. I generally rel

  
## js_constructor_module_pattern.js
myapp.module = (function () {
	// private variables and functions
	var foo = "bar",
		Constuctor;

	// constructor
	Constructor = function () {
	};

	// prototype

## traceTweetLinks.sh
#!/bin/bash
# Recursively follows the first link in a tweet until it reaches the bottom 'root' tweet.
# Built without any testing to trace the origin of this meme: https://twitter.com/sufw/status/433495556300603393
# Published at https://gist.github.com/sufw/8952129

i=0;
startingTweet=$1;

if [ "$#" -ne 1 ]
then

## CheckboxColumnBinding.html
<!DOCTYPE HTML>
<html>
    <head>
        <meta http-equiv="X-UA-Compatible" content="IE=edge" />
        <meta charset="UTF-8">

        <title>Checkbox and Column Binding</title>

        <script id="sap-ui-bootstrap"
                type="text/javascript"

## static_server.js
var express = require('express'),
    open = require('open'),
    app = express(),
    port = process.env.PORT || 8888,
    sapui5 = '/sapui5',
    url = 'http://localhost:' + port + sapui5, // + "/latest";
    year = 60 * 60 * 24 * 365 * 1000;

// Use compress middleware to gzip content
app.use(express.compress());

## readerwithtooling.scala
/**
 * A monad to abstract dependencies in the code, see https://coderwall.com/p/kh_z5g
 */
object Reader {

  /**
   * an implicit to convert a function A => B in a Reader[A, B]
   */
  implicit def reader[C, R](block: C => R): Reader[C, R] = Reader(block)

## anonymous
package au.com.company.mapping;


import java.io.ByteArrayOutputStream;

import java.io.File;

import java.io.FileInputStream;

## launch_sublime_from_terminal.markdown

      
              1 file
            
          
              59 forks
            
          
              79 comments
            
          
              363 stars
            
          
                olivierlacan
                / launch_sublime_from_terminal.markdown
            
            
              Created
              September 5, 2011 15:50
            
              
                Launch Sublime Text 2 from the Mac OS X Terminal
              
          
    Launch Sublime Text 2 from the Mac OS X Terminal

Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
Installation


## node-and-npm-in-30-seconds.sh
echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh
	myapp.module = (function () {
	// private variables and functions
	var foo = "bar",
	Constuctor;

	// constructor
	Constructor = function () {
	};

	// prototype
	#!/bin/bash
	# Recursively follows the first link in a tweet until it reaches the bottom 'root' tweet.
	# Built without any testing to trace the origin of this meme: https://twitter.com/sufw/status/433495556300603393
	# Published at https://gist.github.com/sufw/8952129

	i=0;
	startingTweet=$1;

	if [ "$#" -ne 1 ]
	then
	<!DOCTYPE HTML>
	<html>
	<head>
	<meta http-equiv="X-UA-Compatible" content="IE=edge" />
	<meta charset="UTF-8">

	<title>Checkbox and Column Binding</title>

	<script id="sap-ui-bootstrap"
	type="text/javascript"
	var express = require('express'),
	open = require('open'),
	app = express(),
	port = process.env.PORT \|\| 8888,
	sapui5 = '/sapui5',
	url = 'http://localhost:' + port + sapui5, // + "/latest";
	year = 60 * 60 * 24 * 365 * 1000;

	// Use compress middleware to gzip content
	app.use(express.compress());
	/**
	* A monad to abstract dependencies in the code, see https://coderwall.com/p/kh_z5g
	*/
	object Reader {

	/**
	* an implicit to convert a function A => B in a Reader[A, B]
	*/
	implicit def reader[C, R](block: C => R): Reader[C, R] = Reader(block)
	package au.com.company.mapping;



	import java.io.ByteArrayOutputStream;

	import java.io.File;

	import java.io.FileInputStream;
	echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
	. ~/.bashrc
	mkdir ~/local
	mkdir ~/node-latest-install
	cd ~/node-latest-install
	curl http://nodejs.org/dist/node-latest.tar.gz \| tar xz --strip-components=1
	./configure --prefix=~/local
	make install # ok, fine, this step probably takes more than 30 seconds...
	curl https://www.npmjs.org/install.sh \| sh