caojiafeng nanne007

Server scripts

This is the source for the scripts discussed in https://robots.thoughtbot.com/improving-user-experience-with-shell-scripts

Both scripts are in the bin/ directory of the repo that contains all the markdown documents for blog posts. Users run bin/server and everything is automatically set up for them to view a local preview of the blog. bin/server-setup is a dependency of bin/server and is never run directly by users.

Maitre-d is the name of the "blog engine" discussed in the article.

我的简历

个人信息

曹家锋/男/1992
北京邮电大学/13年本科毕业（智能科学与技术专业）、现硕士在读（计算机技术专业）
手机：17710235744/13261499225
邮箱：[email protected]

2015-01-29 Unofficial Relay FAQ

Compilation of questions and answers about Relay from React.js Conf.

Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.

What is Relay?

Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

So you're curious in learning this new thing called Reactive Programming, particularly its variant comprising of Rx, Bacon.js, RAC, and others.

Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:

Rx.Observable.prototype.flatMapLatest(selector, [thisArg])

Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.

	require 'msgpack'
	require 'thread'

	class ProcessPool
	def initialize(num_process, args={})
	queue_size, worker_class = parse_args([
	:queue_size, nil,
	:worker_class, Worker,
	], args)

	Why do compilers even bother with exploiting undefinedness signed overflow? And what are those
	mysterious cases where it helps?

	A lot of people (myself included) are against transforms that aggressively exploit undefined behavior, but
	I think it's useful to know what compiler writers are accomplishing by this.

	TL;DR: C doesn't work very well if int!=register width, but (for backwards compat) int is 32-bit on all
	major 64-bit targets, and this causes quite hairy problems for code generation and optimization in some
	fairly common cases. The signed overflow UB exploitation is an attempt to work around this.

	#!/bin/bash

	# Build latest version of Emacs, version management with stow
	# OS: Ubuntu 14.04 LTS
	# version: 24.5
	# Toolkit: lucid

	# Warning, use updated version of this script in: https://github.com/favadi/build-emacs

	set -e

	# unicorn_rails -c /data/github/current/config/unicorn.rb -E production -D

	rails_env = ENV['RAILS_ENV'] \|\| 'production'

	# 16 workers and 1 master
	worker_processes (rails_env == 'production' ? 16 : 4)

	# Load rails+github.git into the master before forking workers
	# for super-fast worker spawn times
	preload_app true

	import { Component } from "React";

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