othiym23

The Winterlong Trilogy by Elizabeth Hand

Gothic, Grand Guignol-drenched post-apocalyptic science-fantasy. "Febrile" is a word that comes to mind – the language is overstuffed, it's dense with references to fantasy and folklore, and the characters are run through the wringer. Not the last of her novels to feature a transmogrified Washington DC as a primary venue.

Waking the Moon by Elizabeth Hand

Roman á clef and supernatural romance (in the traditional, not Twilight sense) featuring the hidden war between the Benandanti, a sect of nasty old patriarchal quasi-Catholics, and the forces of Othiym Lunarsa, goddess of a long-suppressed matriarchal death cult. If Camille Paglia ever read this, she probably loved it, but the central story is basically an overheated, fantastic version of Whit Stillman's Metropolitan and so th

airportyh

Browserify Search Request For Help

I have been working on making a search index for npm modules that work with browserify. In order to do this, obviously, for each module on npm, I need to determine whether or not it works with browserify. Easy! I thought. I will run the browserify cli tool on the module browserify node_modules/that_module, and if it exits normally, it works with browserify. So I did that, and implemented a search engine on this premise. Except that, in the search results, I found a lot of modules which, although it "passed the test", they still were useless because simple the act of loading the bundle in a browser would result in a runtime error - a lot of these were a result of the module testing for process.versions.node which doesn't exist in the browserify process shim. Okay, I thought, I'll run the resulting bundle in jsdom, genious! That did reject lots of modules, but it still wasn't good enough. I still got a lot of modules in the search inde

mikeal

I've known people at nodejitsu for years, since before the company even existed. I still consider many of them friends. That said, somebody over there has lost their mind.

Trademarks are an important part of open source. They protect the integrity of the trust that is built by any project. A classic example of why this is the case is Firefox. Suppose that a malware producer takes the Firefox codebase, which is free and open source, packages up their malware with it and then releases it as "Firefox". Then they buy search advertising and suddenly their bad and malicious version of Firefox is the first result on search engines across the web. This is clearly a bad thing for Firefox and open source everywhere, but what can Mozilla do to protect their community of users?

They can't enforce a software license since the use is permitted under the Mozilla Public License. They can, however, enforce on these hypothetical bad actors using their trademark on the word "Fi

mikeal

Children are created, raised, cared for and we hope that they will live a long and proud life only to end long after their creator's has ended. They are their creator's legacy.

Your code is not your child, it is an animal raised for slaughter. Your code will die. It will die before your death. Your code's entire purpose is to die. Your code enables some new function and if successful that new function will grow, it will mature, it will eventually outlive the usefullness you've provided. When successful your code creates value that outlives it and the faster the better. When unsuccessful a mercy killing is most appropriate.

Believing that our code is our children makes us territorial, protective. Nobody is allowed to kill it, only improve it. The idea that our code can be perfect, that it can change to handle so many new concerns leads to the birth of frameworks and plugin systems. These systems brutalize creativity by forcing new value to conform to the standards of our aging children.

xdamman

#!/bin/bash
git clone https://github.com/TryGhost/Ghost.git
cd Ghost
git submodule update --init
sudo gem install sass && sudo gem install sass
sudo npm install -g grunt-cli
npm install
grunt init
npm start
open "http://localhost:2368/ghost/"

mikeal

This is rather out of date and we've all moved past it. Me and Issac are cool now.

jpetazzo

Unionize: network superpowers for your docker containers

Unionize lets you connect together docker containers in arbitrarily complex scenarios.

Note: I recommend to use https://github.com/jpetazzo/pipework instead.

• pipework is a better name than unionize
• it's hosted on a "real" github repo instead of a small gist :-)

Now if you want Unionize, it's still here. Just check those examples.

mbbx6spp

#!/usr/bin/env bash

PERCONA_PW=$1
DEBCONF_PREFIX="percona-server-server-5.5 percona-server-server"

[ ! $# -eq 1 ] && echo "Usage: $0 PASSWORD" && exit 1;

gpg --keyserver  hkp://keys.gnupg.net --recv-keys 1C4CBDCDCD2EFD2A 
gpg -a --export CD2EFD2A | sudo apt-key add -                      
sudo sh -c 'cat <<EOF >/etc/apt/sources.list.d/percona.list