start new:
tmux
start new with session name:
tmux new -s myname
# Key considerations for algorithm "RSA" ≥ 2048-bit
openssl genrsa -out server.key 2048
# Key considerations for algorithm "ECDSA" ≥ secp384r1
# List ECDSA the supported curves (openssl ecparam -list_curves)
var Bar1 = base => class extends base { | |
componentWillMount(){ | |
super.componentWillMount(); | |
console.log('Bar1'); | |
} | |
}; | |
var Bar2 = base => class extends base { | |
componentWillMount(){ | |
super.componentWillMount(); |
React has revolutionized the way we write user interfaces. It brings an extremely simple mental model to the authoring of UIs. React-native, react-canvas, and other projects have shown us that this model extends beyond the browser DOM.
I believe that this functional, predictable approach can also revolutionize how we build real-world user interfaces.
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
import RelayStoreData from 'react-relay/lib/RelayStoreData'; | |
import RelayQueryPath from 'react-relay/lib/RelayQueryPath'; | |
import printRelayQuery from 'react-relay/lib/printRelayQuery'; | |
import {List,Map} from 'immutable'; | |
var REMOVE_KEYS = [ | |
'_storage' | |
]; |
let rootValue = { | |
response: { | |
timing: { | |
fields: [] | |
} | |
} | |
} | |
const start = new Date().getTime(); | |
return graphql(schema, query, rootValue, variables).then(response => { |
import React from 'react' | |
const { number, func, array, shape } = React.PropTypes | |
export default React.createClass({ | |
propTypes: { | |
itemHeight: number.isRequired, | |
renderItem: func.isRequired, | |
items: array.isRequired, |
// " In short, the closer the code is to a description of “what I want the program to do”, the better." | |
// http://staltz.com/why-react-redux-is-an-inferior-paradigm.html | |
//////////////////////////////////////////////////////////////////////////////// | |
// Cycle | |
import {Observable} from 'rx'; | |
import Cycle from '@cycle/core'; | |
import {div, button, p, makeDOMDriver} from '@cycle/dom'; | |
function main({DOM}) { |