| { nixpkgs ? <nixpkgs>, system ? builtins.currentSystem }: | |
| with import nixpkgs { inherit system; }; | |
| let nix = enableDebugging nixUnstable; in | |
| runCommand "test" | |
| { buildInputs = [ nix boehmgc ]; dontStrip = true; } | |
| '' | |
| mkdir -p $out/bin/ |
| import GHCJS.DOM.Types (Element, unElement) | |
| import GHCJS.DOM.Element (toElement) | |
| import GHCJS.Prim (JSRef) | |
| -- http://www.getmdl.io/started/index.html#dynamic | |
| #ifdef __GHCJS__ | |
| foreign import javascript unsafe "componentHandler.upgradeElement($1);" | |
| materialInitJS :: JSRef Element -> IO () | |
| #else | |
| materialInitJS = error "y u no javascript?" |
| # [PackageDev] target_format: plist, ext: tmLanguage | |
| # Made by Wout.Mertens@gmail.com | |
| # This grammar tries to be complete, but regex-based highlighters | |
| # can't be full parsers. Therefore it's a bit looser than the Nix | |
| # parser itself and some legal constructs will be marked as illegal. | |
| # It seems to work fine for nixpkgs. | |
| # Cute hacks: Check out the attrset-for-sure and friends definitions | |
| --- | |
| name: Nix | |
| scopeName: source.nix |
This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.
The script is here:
#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"
| # vim: ft=bash ts=2 sw=2 sts=2 | |
| # | |
| # agnoster's Theme - https://gist.github.com/3712874 | |
| # A Powerline-inspired theme for BASH | |
| # | |
| # (Converted from ZSH theme by Kenny Root) | |
| # | |
| # # README | |
| # | |
| # In order for this theme to render correctly, you will need a |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real