bitttttten

Intro

This pattern is for those of you that maintain multiple applications and need to build components that can be reused across all these apps. It won’t be useful if you build components meant to be reused in the same application.

Your typical app structure

If you use smart/dumb, or container/presentational components, which you should if you want your components to be at least a little reusable, your typical application might look like this:

Algorithmic layouts

You are looking at the most important, and most abundant thing on the web. You can't see it, unfortunately, because it's very small… aaaaand it's invisible — so having a magnifying glass doesn't really help here. But still.

I'm talking, of course, about U+0020; not to be confused with the band U2, who are just as ubiquitous, but far less useful.

This unicode point, representing the humble space character, is between every word, in every run of text, on every page of the web. And it has a very special characteristic: it's not sticky like glue. If two words are neighbors but there's not enough room for both of them, the space will free the second word to wrap around and start a new line.

Before getting into flexible containers, viewport meta tags, and @media breakpoints this humble character is what makes the web fundamentally 'responsive'. That is: able to change the layout of its content to suit different devices, contexts, and settings. Browser text does this automa

Implementation notes on react's scheduling model as of (shortly before) 16.8.0

While the public API intended for users to use is the scheduler package, the reconciler currently does not use scheduler's priority classes internally.

ReactFiberScheduler has its own internal "mini-scheduler" that uses the scheduler package indirectly for its deadline-capable scheduleCallback.

This is kind of a documentation of implementation details that I suppose will be gone by the end of the year, but what can you do.

	Latency Comparison Numbers (~2012)
	----------------------------------
	L1 cache reference 0.5 ns
	Branch mispredict 5 ns
	L2 cache reference 7 ns 14x L1 cache
	Mutex lock/unlock 25 ns
	Main memory reference 100 ns 20x L2 cache, 200x L1 cache
	Compress 1K bytes with Zippy 3,000 ns 3 us
	Send 1K bytes over 1 Gbps network 10,000 ns 10 us
	Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD


	#include "hemicube.h"

	#define PACK_HEMICUBES 1


	static void get_hemicube_face_normal(int index, Vector3 forward, Vector3 left, Vector3 *up) {
	// Unwrapped hemicube with positive-Z in the middle.
	switch (index) {
	case 0: forward = Vector3(+1, 0, 0); left = Vector3( 0, 1, 0); break;

	http://ogp.me/
	https://moz.com/blog/meta-data-templates-123

	https://search.google.com/structured-data/testing-tool
	https://developers.facebook.com/tools/debug/og/object - https://developers.facebook.com/docs/reference/opengraph
	https://cards-dev.twitter.com/validator - https://dev.twitter.com/cards/types
	https://developers.pinterest.com/tools/url-debugger/ - https://developers.pinterest.com/docs/rich-pins/overview/

	https://developer.linkedin.com/docs/share-on-linkedin

	function createStore (reducers) {
	var state = reducers()
	const store = {
	dispatch: (action) => {
	state = reducers(state, action)
	},
	getState: () => {
	return state
	}
	}

	import React from "react";
	import ReactDOM from "react-dom";
	import PropTypes from "prop-types";

	document.body.style.background = `
	linear-gradient(135deg,
	#1e5799 0%,
	#2989d8 50%,
	#207cca 51%,
	#7db9e8 100%