| *.tfbackup | |
| .terraform/ | |
| *.tfstate | |
| .terraform.tfstate.lock.info |
| #!/usr/bin/env bash | |
| # MIT © Sindre Sorhus - sindresorhus.com | |
| # git hook to run a command after `git pull` if a specified file was changed | |
| # Run `chmod +x post-merge` to make it executable then put it into `.git/hooks/`. | |
| changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)" | |
| check_run() { | |
| echo "$changed_files" | grep --quiet "$1" && eval "$2" |
The git command-line utility has plenty of inconsistencies http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/
A GUI like http://sourcetreeapp.com is often helpful, but staying on the command line usually quicker. This is a list of the commands I use most frequently, listed by functional category:
git status list which (unstaged) files have changed
| /*! CSS.supports() Polyfill | |
| * https://gist.github.com/codler/03a0995195aa2859465f | |
| * Copyright (c) 2014 Han Lin Yap http://yap.nu; MIT license */ | |
| if (!('CSS' in window)) { | |
| window.CSS = {}; | |
| } | |
| if (!('supports' in window.CSS)) { | |
| window.CSS._cacheSupports = {}; | |
| window.CSS.supports = function(propertyName, value) { |
made with esnextbin
made with esnextbin
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParentelem.clientLeft, elem.clientTop, elem.clientWidth, elem.clientHeightelem.getClientRects(), elem.getBoundingClientRect()
| console.clear() | |
| const l = 1; | |
| const j = 1; | |
| const m = 2; | |
| const k = 2; | |
| const d = 2; | |
| const expression = [] |
tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
How do we solve this with React?
made with esnextbin