Ramnath Vaidyanathan ramnathv
I've done the same process every couple years since 2013 (Mountain Lion, Mavericks, High Sierra, Catalina) and I updated the Gist each time I've done it.
I kinda regret for not using something like Boxen (or anything similar) to automate the process, but TBH I only actually needed to these steps once every couple years...
| var stringify = function(obj, prop) { | |
| var placeholder = '____PLACEHOLDER____'; | |
| var fns = []; | |
| var json = JSON.stringify(obj, function(key, value) { | |
| if (typeof value === 'function') { | |
| fns.push(value); | |
| return placeholder; | |
| } | |
| return value; | |
| }, 2); |
| #!/usr/bin/env ruby | |
| # Generate a dbdiagram for dbdiagram.io from a dbt project. | |
| # | |
| # Usage: | |
| # 1. Run `dbt docs generate` first. | |
| # 2. Run `dbt_to_dbdiagram.rb` | |
| # 3. Paste the output in https://dbdiagram.io/ | |
| require 'yaml' | |
| require 'json' |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
| // Browser fingerprinting is a technique to "mark" anonymous users using JS | |
| // (or other things). To build an "identity" of sorts the browser is queried | |
| // for a list of its plugins, the screen size and several other things, then | |
| // hashes them. The idea is that these bits of information produce an unique | |
| // "fingerprint" of sorts; the more elaborate the list of data points is, the | |
| // more unique this fingerprint becomes. And you wouldn't even need to set a | |
| // cookie to recognize this user when she visits again. | |
| // | |
| // For more information on this topic consult | |
| // [Ars Technica](http://arstechnica.com/tech-policy/news/2010/05/how-your-web-browser-rats-you-out-online.ars) |
Clearly ES6 is a huge improvement over ES5, and tools like [6to5][] allow us to use these cool features now. I was reading [Replace CoffeeScript with ES6][replace coffeescript] by [Blake Williams][] and thought it was a great summary of how ES6 solves many of the same problems that CoffeeScript solves; however I'd like to comment on a few of Blake's points and talk about why I'll be sticking with CoffeeScript.
Classes in ES6 (like many of the syntax changes in ES6) are very similar to the CoffeeScript equivalent. To support browsers that are not fully ES5 compliant (e.g. IE8-), however, we still can't really use getters/setters, so ignoring these the comparison is:
| # This example demonstrates running furrr code distributed on 2 AWS instances ("nodes"). | |
| # The instances have already been created. | |
| library(future) | |
| library(furrr) | |
| # Two t2.micro AWS instances | |
| # Created from http://www.louisaslett.com/RStudio_AMI/ | |
| public_ip <- c("34.205.155.182", "34.201.26.217") |