Heaven NE-SmallTown

What forces layout / reflow

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.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

Pattern Matching

This is a strawman proposal for adding pattern matching to ECMAScript. Pattern matching is useful for matching a value to some structure in a similar way to destructuring. The primary difference between destructuring and pattern matching are the use cases involved - destructuring is useful for binding pieces out of larger structures whereas pattern matching is useful for mapping a value's structure to data or a set of behaviors. In practice this means that destructuring tends to allow many shapes of data and will do its best to bind something out of it, whereas pattern matching will tend to be more conservative.

Additionally, the power of pattern matching is increased substantially when values are allowed to participate in the pattern matching semantics as a matcher as well as a matchee. This proposal includes the notion of a pattern matching protocol - a symbol method that can be implemented by objects that enables developers to use those values in pattern matching. A common scenario w

Bridging Native & React for iOS & Android

js -> native

native -> js

清除safari缓存即可。
原理是因为Apple限制，在iOS上微信只能使用webview。

	import { Component } from "React";

	export var Enhance = ComposedComponent => class extends Component {
	constructor() {
	this.state = { data: null };
	}
	componentDidMount() {
	this.setState({ data: 'Hello' });
	}
	render() {

	// store.js
	let {store, handler} = sto(initialState, reduceFn); // where reduceFn: function(currentState, action, ...args){}

	dispatcher.register(handler);
	export store;

	// elsewhere
	store.get() // -> current state

	store.toObservable() // -> to be used with .observe()

	/**
	* Stores are just seed + reduce function.
	* Notice they are plain objects and don't own the state.
	*/
	const countUpStore = {
	seed: {
	counter: 0
	},

	reduce(state, action) {

	/**
	* Basic proof of concept.
	* - Hot reloadable
	* - Stateless stores
	* - Stores and action creators interoperable with Redux.
	*/

	import React, { Component } from 'react';

	export default function dispatch(store, atom, action) {

	import {fk, many, Model} from 'redux-orm';

	class Book extends Model {
	static get fields() {
	authors: many('Author', 'books'),
	publisher: fk('Publisher', 'books'),
	}

	static parse(data) {
	/*

	var MY_CONSTANT = 42

	// Implementation of a class
	var MyClass = function () {
	// constructor
	}
	MyClass.prototype.getAnswer = function () {
	return MY_CONSTANT
	}