Feynman_W iDevSpread

Install

Modify index.txt with your output path and proxy info
Use Text Builder to build configuration for Surge: $ text-builder -index /path/to/index.txt Or run $ sh build-all to build all your index files.
Import configuration via AirDrop/iTunes/Dropbox/iCloud

本人不提供任何保证和技术支持，使用者自负风险。
There are no guarantees, no any support. Use it at your own risk.

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2:

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

	# 你可以从该 URL 下载这个配置文件: http://surge.run/config-example/ios.conf
	# 用编辑器编辑后，再通过 iTunes, URL, AirDrop 或者 iCloud Drive 复制回 iOS 设备
	# Version 2.0

	[General]
	# 日志等级: warning, notify, info, verbose (默认值: notify)
	loglevel = notify
	# 跳过某个域名或者 IP 段，这些目标主机将不会由 Surge Proxy 处理。(在 macOS
	# 版本中，如果启用了 Set as System Proxy, 那么这些值会被写入到系统网络代理
	# 设置中.)

	[General]
	loglevel = notify
	skip-proxy = 127.0.0.1, 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12, 100.64.0.0/10, localhost, *.local, ::ffff:0:0:0:0/1, ::ffff:128:0:0:0/1
	bypass-tun = 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12

	# dns-server = 119.29.29.29,223.5.5.5,114.114.115.115
	# external-controller-access = [email protected]:6155
	# ipv6 = true

	// REMEMBER TO CHANGE THE external-controller-access' PASSWORD

	/*
	Swift Programming Language Guide
	"A Swift Tour" Solutions
	https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.html#//apple_ref/doc/uid/TP40014097-CH2-XID_1

	These are the solutions to all the "experiments" in the pre-release Swift Programming Guide
	(released on the same day Apple announced Swift). A couple of things worth noting:

	1. Swift syntax, e.g. array declarations, has changed since I releasd these. So this code will
	probably cause some errors when you paste it into a playground. Should be easy enough to fix