Yosh yoshuawuyts

Nix seems perfect for developers - until I try to use it...

Want to use Nix for development but you're not sure how? Concerned about the fluidity of nixpkgs channels or not being able to easily install arbitrary package versions?

When I first heard about Nix it seemed like the perfect tool for a developer. When I tried to actually use it for developing and deploying web apps, though, the pieces just didn't seem to add up.

Tests

✔ Platform [pass: 1, fail: 0, duration: 1ms]
✔ init [pass: 22, fail: 0, duration: 1ms]
✔ emit [pass: 27, fail: 0, duration: 12ms]
✔ emit with context [pass: 42, fail: 0, duration: 5ms]
✔ emit one value - two listeners [pass: 57, fail: 0, duration: 2ms]
✔ emit one value - one listener [pass: 40, fail: 0, duration: 1ms]
✔ emit many listeners [pass: 30, fail: 0, duration: 1ms]

TAP version 13

Platform

ok 1 (unnamed assert) Node.js 6.2.1 on Linux 64-bit

1..1

tests 1

pass 1

ok

Fast Loading a SPA with a single request

Authors

Motivation

We need an Open Source alternative to AMP.

	var wswarm = require('webrtc-swarm')
	var signalhub = require('signalhub')
	var swarm = wswarm(signalhub(
	'swarmchat-example',
	['https://signalhub.mafintosh.com']
	))
	var randombytes = require('randombytes')

	var vdom = require('virtual-dom')
	var h = vdom.h

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else

	const choo = require('choo')
	const app = choo()

	function view (params, state, send) {
	return choo.view`
	<main>

	20:04 < ahdinosaur> if anyone is interested in a choo-like API where it's pull-streams all the way down, i made some helpers for `inu`: https://github.com/ahdinosaur/inux
	20:04 < yoshuawuyts> ahdinosaur: I'm curious: how big is inu?
	20:04 < yoshuawuyts> probably smaller than choo I'd think
	20:05 < yoshuawuyts> well, inux would be more fair to compare I reckon but still
	20:05 < ahdinosaur> one sec, i'll discify
	20:05 < yoshuawuyts> ahdinosaur: I'm using this for choo https://github.com/yoshuawuyts/choo/blob/master/scripts/instrument#L24-L35
	20:06 < yoshuawuyts> gzip size tends to translate slightly better I find
	20:06 < ronnross> So curious how one would use something like https://codemirror.net/ in Choo.
	20:07 < ronnross> Would you work directly with the dome of use subscriptions to handle working with it.
	20:07 < ronnross> Might sound like a crazy question, but when I implemented it in Elm I had to use ports and subscriptions.

	alias ..='cd ..'
	alias ls='gls --color=auto'
	alias ll='ls -lh --group-directories-first'
	alias slt='open -a "Sublime Text"'
	alias npm-offline="npm --cache-min Infinity "
	alias publish='git push && git push --tags && npm publish'
	alias nodeir='node --trace-hydrogen --trace-phase=Z --trace-deopt --code-comments --hydrogen-track-positions --redirect-code-traces --redirect-code-traces-to=code.asm --print-opt-code --trace_hydrogen_file=hydrogen.cfg'

	export HISTCONTROL=ignoredups
	export PS1="\[\033[44m\] \W \[\033[49m\]\[\033[42m\]\$(__git_ps1 \" %s \")\[\033[49m\] "

	if (window.requestAnimationFrame) {
	function checkForJank () { // eslint-disable-line no-inner-delcarations
	const frameStart = Date.now()
	window.requestAnimationFrame(() => {
	const frameDuration = Date.now() - frameStart
	if (frameDuration > 17) {
	Perf.log(FirstJank)
	} else {
	checkForJank()
	}