devin ivy devinivy

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

Glob Up and Running

To test a glob pattern go over to globtester and play around with creating your own file structure online, it's super easy to get started that way.

If you want to test out a glob pattern in the terminal use echo followed by the pattern, for instance.

echo **/*.js

Disclaimer

I'm still very new to Kafka, eventsourcing, stream processing, etc. I'm in the middle of building my first production system with this stuff and am writing this at the request of a few folks on Twitter. So if you do have experience, please do me and anyone else reading this a favor by pointing out things I get wrong :)

Inspirations

The Log — http://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying
Turning the database inside out — http://www.confluent.io/blog/2015/03/04/turning-the-database-inside-out-with-apache-samza/
Why local state is a fundamental primitive in stream processing — http://radar.oreilly.com/2014/07/why-local-state-is-a-fundamental-primitive-in-stream-processing.html
Samza
Various functional systems been exposed to over past year or so, React, Flux, RX, etc.

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on

	I inlined the code from microAjax there, to keep dependencies at 0. I think the following cite satisfies the license?

	https://code.google.com/archive/p/microajax/

	This code was referenced extensively:
	https://bitbucket.org/snippets/jdubray/9dgKp/sam-sample

	fn main() {

	let closure_immutable_pure = \|x: i32\| x + 1;

	let result1 = apply_pure(& closure_immutable_pure, 1);
	// let result2 = apply_mut(&mut closure_immutable_pure, 2); // not typeable
	let result3 = apply_once(closure_immutable_pure, 3);

	let mut closure_mutable_pure = \|x: i32\| x + 1;

	version: 0.0
	os: linux
	files:
	- source: /
	destination: /home/ec2-user/node
	permissions:
	- object: /home/ec2-user
	owner: ec2-user
	group: ec2-user
	type:

	<!--
	Behavior to connect your NuclearJS app to Polymer.

	Add key 'bindNuclear' to your property with as value a
	valid NuclearJS getter.

	Adapted from the NuclearJS ReactJS mix-in:
	https://github.com/jordangarcia/nuclear-react-mixin
	-->
	<dom-module id='nuclear-example'>

	{
	"name": "polymer-globals-behavior",
	"dependencies": {
	"polymer": "Polymer/polymer#~1.0.5"
	}
	}