314 karma · joined June 16, 2011
I'm not sure what you mean. If you're referring to the implementation, it's around three hundred lines [0], including the unfortunate problem I mention with visiting expressions, which doesn't seem like a lot.
Maybe you mean the instrumented code, but that doesn't matter -- it's meant to be generated, executed and thrown away. You would never have to look at it.
[0]: http://www.pluralsight.com/search/?searchTerm=play%20by%20pl...
[0]: https://www.cs.utexas.edu/~EWD/ewd10xx/EWD1001.PDF [1]: http://www.cs.utexas.edu/users/EWD/
pics := media -> pictures
pic := pics -> random
pic -> tint (colors -> sepia)
c := colors -> blue
All the components are there but not in the right order -- it still tints with the default color. function mkvirtualenv {
virtualenv "$HOME/.virtualenvs/$1"
if [ $# -eq 2 ]; then
vex "$1" pip install -r "$2"
fi
}
function lsvirtualenv {
ls "$HOME/.virtualenvs"
}
function rmvirtualenv {
rm -rf "$HOME/.virtualenvs/$1"
}I don't think "hosted git" accurately captures the appeal of GitHub (or bitbucket for that matter). While this is the main premise behind both products, I don't think they're necessarily interchangeable in the way you describe.
Also, if e.g. a research group already has a GitHub organization with their open source work (many do), then it's reasonable for them to want private repos under the same umbrella so that they can collaborate using the same tools irrespective of whether the work is open yet.
"We're making the world a better place. By constructing elegant hierarchies for maximum code reuse and extensibility."
"Making the world a better place. Through minimal message-oriented transport layers."