edwardbeckett

-server
-Xms2g
-Xmx2g
-Xss16m
-XX:+UseConcMarkSweepGC
-XX:+CMSParallelRemarkEnabled
-XX:ConcGCThreads=4
-XX:ReservedCodeCacheSize=128m
-XX:+AlwaysPreTouch
-XX:+TieredCompilation

iangreenleaf

Rails naming conventions

General Ruby conventions

Class names are CamelCase.

Methods and variables are snake_case.

Methods with a ? suffix will return a boolean.

mikroskeem

#!/usr/bin/env bash

0x0() {
    case "${1}" in
        "s")
            shift
            local url=`curl --silent -F"shorten=${1}" https://0x0.st | sed 's/\n//'`
            echo -n "${url}"
            ;;
        "u")

avalonalex

   sudo rm -rf /Library/Frameworks/GHC.framework
   sudo rm -rf /Library/Frameworks/HaskellPlatform.framework
   sudo rm -rf /Library/Haskell
   rm -rf .cabal
   rm -rf .ghc
   rm -rf ~/Library/Haskell
   find /usr/bin /usr/local/bin -type l | \
     xargs -If sh -c '/bin/echo -n f /; readlink f' | \
     egrep '//Library/(Haskell|Frameworks/(GHC|HaskellPlatform).framework)' | \
     cut -f 1 -d ' ' > /tmp/hs-bin-links

somebox

#!/bin/bash

# A script to set up a new mac. Uses bash, homebrew, etc.

# Focused for ruby/rails development. Includes many utilities and apps:
# - homebrew, rvm, node
# - quicklook plugins, terminal fonts
# - browsers: chrome, firefox
# - dev: iterm2, sublime text, postgres, chrome devtools, etc.
# - team: slack, dropbox, google drive, skype, etc

dotcomputercraft

the best way (I've found) to completely uninstall node + npm is to do the following:

go to /usr/local/lib and delete any node and node_modules
go to /usr/local/include and delete any node and node_modules directory
if you installed with brew install node, then run brew uninstall node in your terminal
check your Home directory for any local or lib or include folders, and delete any node or node_modules from there
go to /usr/local/bin and delete any node executable
You may need to do the additional instructions as well:

sudo rm /usr/local/bin/npm

jamesattard

echo "Fixing ownership and permissions..."
chmod -R 755 /System/Library/Extensions/*
chown -R root:wheel /System/Library/Extensions/*
chown root:admin /
echo "Rebuilding kext cache..."
kextcache -system-prelinked-kernel
kextcache -system-caches

stevenswafford

"          _                      _          "
"   _     /||       .   .        ||\     _   "
"  ( }    \||D    '   '     '   C||/    { %  "
" | /\__,=_[_]   '  .   . '       [_]_=,__/\ |"
" |_\_  |----|                    |----|  _/_|"
" |  |/ |    |                    |    | \|  |"
" |  /_ |    |                    |    | _\  |"

	It is all fun and games until someone gets hacked!

lopezjurip

{
    "cmd": ["g++ $file -o $file_base_name -I/usr/local/include ; ./$file_base_name"],
    "selector": "source.c++",
    "shell": true
}

kentbrew

Signing a Self-Hosted Auto-Updating Firefox Extension under the New Regime

I run a self-hosted auto-updating Firefox add-on being used by several million people. I am informed that I will need to "sign" it soon or it will quit working. (Deadlines are unclear; it seems like it may be as soon as June 30th.) I am looking for exact instructions as to how to make this happen.

I am not finding these instructions, so I am doing my best to puzzle things out.

Googling for things like "how to sign a firefox add-on" get me a lot of false leads. Mozilla should take down or at least modify these pages with current information:

https://developer.mozilla.org/en-US/docs/Signing_a_XPI

https://developer.mozilla.org/en-US/docs/Signing_an_extension