Jeongho Jeong JeongHoJeong

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

Why using the `children` prop makes `React.memo()` not work

I've recently ran into a pitfall of [React.memo()][memo] that seems generally overlooked; skimming over the top results in Google just finds it mentioned in passing in a [React issue][regit], but not in the [FAQ] or API [overview][react-api], and not in the articles that set out to explain React.memo() (at least the ones I looked at). The issue is specifically that nesting children defeats memoization, unless the children are just plain text. To give a simplified code example:

const Memoized = React.memo(({ children }) => (<div>{children}</div>));
// Won't ever re-render
<Memoized>bar</Memoized>
// Will re-render every time; the memoization does nothing

Run node app in background

Running a script in the background in linux can be done using nohup, using nohup we can run node application in the background

$ nohup node server.js > /dev/null 2>&1 &

nohup means: Do not terminate this process even when the stty is cut off
> /dev/null means: stdout goes to /dev/null (which is a dummy device that does not record any output)

1. Get LLVM 7 compiled with webassembly support.

You'll need LLVM to output to the WASM target. This has just been added by default in trunk, so if LLVM >7 is available, you might be able to just brew install llvm.

If you have wasm support already you should see:

$ llc --version

running:

bash create-vod-hls.sh beach.mkv

will produce:

    beach/
      |- playlist.m3u8
 |- 360p.m3u8

	#!/usr/bin/env bash
	set -euo pipefail

	# === CONFIGURATION ===
	APP_SRC="/Applications/Fork.app"
	APP_DEST="./Fork.app"
	DYLIB_NAME="ColorTap.dylib"
	COLOR_SRC="ColorTap.m"
	INSERT_REPO="https://github.com/Tyilo/insert_dylib.git"

	import { promises } from "fs";
	import crypto from "crypto";
	import path from "path";
	import { print, parse } from "graphql";

	const plugin = {
	name: "relay",
	setup: build => {
	build.onLoad({ filter: /\.tsx$/, namespace: "" }, async args => {
	let contents = await promises.readFile(args.path, "utf8");

	import React from 'react';

	const GUESSED_HEIGHT = 80; // Initial height value we will use for unknown itme height

	type Data = {
	id: number,
	value: string,
	};

	type VirtualScrollerProps = {

Service	Type	Storage	Limitations
Amazon DynamoDB	⚠️ Proprietary NoSQL	25 GB	⚠️ Payment method required
Amazon RDS	⚠️ Proprietary RDBMS		⚠️ Only free for 1 year
Azure SQL Database	MS SQL Server		⚠️ Only free for 1 year
👉 Clever Cloud	PostgreSQL, MySQL, MongoDB, Redis	256 MB (PostgreSQL)	Max 5 connections (PostgreSQL)

	//----------------------------------*\
	// TRIGONOMETRY FUNCTIONS
	//----------------------------------*/

	// # Trigonometry in CSS
	//
	// - Through Taylor/Maclaurin polynomial representation: http://people.math.sc.edu/girardi/m142/handouts/10sTaylorPolySeries.pdf
	// - Useful if you don't want to use JS.
	// - With CSS Variables.
	// - `calc()` can't do power (x ^ y) so I used multiplication instead.

Jeongho Jeong JeongHoJeong

Why using the children prop makes React.memo() not work

Run node app in background

1. Get LLVM 7 compiled with webassembly support.

Why using the `children` prop makes `React.memo()` not work