| # Pass the env-vars to MYCOMMAND | |
| eval $(egrep -v '^#' .env | xargs) MYCOMMAND | |
| # … or ... | |
| # Export the vars in .env into your shell: | |
| export $(egrep -v '^#' .env | xargs) |
Use docker-machine to lay down 3 x hosts on AWS using docker-engine 1.12
docker-machine create --driver amazonec2 --amazonec2-private-address-only --engine-install-url https://test.docker.com/ levenson-docker-swarm-manager1
docker-machine create --driver amazonec2 --amazonec2-private-address-only --engine-install-url https://test.docker.com/ levenson-docker-swarm-worker1
| if (typeof Promise === 'undefined') { | |
| require.ensure([], (require) => { | |
| require('imports?this=>window!es6-promise') | |
| }) | |
| } | |
| if (typeof fetch === 'undefined') { | |
| require.ensure([], (require) => { | |
| require('imports?self=>window!whatwg-fetch') | |
| }) |
This is a proposal for a lightning talk at the Reactive 2015 conference.
NOTE: If you like this, star ⭐ the Gist - the amount of stars decides whether it makes the cut!
React just got stateless components, meaning that they are in essence pure functions for rendering. Pure functions make it dead simple - even fun - to refactor your views
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.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
The 0.13.0 improvements to React Components are often framed as "es6 classes" but being able to use the new class syntax isn't really the big change. The main thing of note in 0.13 is that React Components are no longer special objects that need to be created using a specific method (createClass()). One of the benefits of this change is that you can use the es6 class syntax, but also tons of other patterns work as well!
Below are a few examples creating React components that all work as expected using a bunch of JS object creation patterns (https://github.com/getify/You-Dont-Know-JS/blob/master/this%20&%20object%20prototypes/ch4.md#mixins). All of the examples are of stateful components, and so need to delegate to React.Component for setState(), but if you have stateless components each patterns tends to get even simpler. The one major caveat with react components is that you need to assign props and context to the component instance otherwise the component will be static. The reason is
| var i = 0; | |
| maybeSyncMaybeAsync(function(){ | |
| i++; | |
| }); | |
| console.log("The value of i is", i); |
| var co = require('co'); | |
| //var Promise = require('bluebird'); | |
| //var Promise = require('promise'); | |
| var count = 0; | |
| co(function* () { | |
| while (true) { | |
| count++; | |
| try { | |
| yield getData(); |
