Andrii Tytar faustman

JSConf Slides, Codes and Notes

These are all the JSConf 2014 slides, codes, and notes I was able to cull together from twitter. Thanks to the speakers who posted them and thanks to @chantastic for posting his wonderful notes.

Modular frontend with NPM - Jake Verbaten (@Raynos)

THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.

PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

Deploy Rails 4 app with Dokku on DigitalOcean

Install dokku

First create a Ubuntu 13.04 x64 droplet on DigitalOcean Control Panel

Then ssh with root account, run this in termianl:

$ wget -qO- https://raw.github.com/progrium/dokku/master/bootstrap.sh | sudo bash

A slightly updated version of this doc is here on my website.

Why I Like Go

I visited with PagerDuty yesterday for a little Friday beer and pizza. While there I got started talking about Go. I was asked by Alex, their CEO, why I liked it. Several other people have asked me the same question recently, so I figured it was worth posting.

Goroutines

The first 1/2 of Go's concurrency story. Lightweight, concurrent function execution. You can spawn tons of these if needed and the Go runtime multiplexes them onto the configured number of CPUs/Threads as needed. They start with a super small stack that can grow (and shrink) via dynamic allocation (and freeing). They are as simple as go f(x), where f() is a function.

I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.

From Require.js - Why AMD:

The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"

I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.

	//TODO: make this a module

	/**
	* # SockJS socket management service
	*
	* Creates SockJS socket connection to server, re-connects on disconnection,
	* and exports hooks to map handlers for various data interactions.
	*
	*/
	angular.module('app').factory

	# A simple Makefile alternative to using Grunt for your static asset compilation
	#
	## Usage
	#
	# $ npm install
	#
	# And then you can run various commands:
	#
	# $ make # compile files that need compiling
	# $ make clean all # remove target files and recompile from scratch

	-- Two dashes start a one-line comment.

	--[[
	Adding two ['s and ]'s makes it a
	multi-line comment.
	--]]

	----------------------------------------------------
	-- 1. Variables and flow control.
	----------------------------------------------------

	#!/bin/bash
	#
	# Copy data from a Time Machine volume mounted on a Linux box.
	#
	# Usage: copy-from-time-machine.sh <source> <target>
	#
	# source: the source directory inside a time machine backup
	# target: the target directory in which to copy the reconstructed
	# directory trees. Created if it does not exists.
	#