Sergey Korochansky SergeyKorochansky

DIY CoffeeScript source map support

CoffeeScript already has source map support via the -m flag, but you have to compile the .coffee first and then run the .js with node for it to be effective. Running the .coffee directly with coffee seems to have no source map support.

This hack recalculates (and caches in memory) the source map on the fly so it can be imported into the excellent source-map-support module. It's disabled if you run the compiled JS file directly (as you would in production) because it assumes the source maps will already have been generated.

Books

Concepts-Techniques-Models-Computer-Programming CMT это известная книжка CMT, за которой слава закрепилась не хуже чем у SICP

это из этой книжки классификация различных парадигм Если присмотришься, то увидишь, что Oz поддерживает большинство вариаций (с этой целью его и конструировали, чтобы можно было наглядно продемонстрировать различные подходы в одном языке)

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

Backend Architectures

Twitter

ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats

Update May 2017

Eric Bidelman has documented some of the common workflows possible with headless Chrome over in https://developers.google.com/web/updates/2017/04/headless-chrome.

Update

If you're looking at this in 2016 and beyond, I strongly recommend investigating real headless Chrome: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md

Windows and Mac users might find using Justin Ribeiro's Docker setup useful here while full support for these platforms is being worked out.

Since this is on Hacker News and reddit...

No, I don't distribute my résumé like this. A friend of mine made a joke about me being the kind of person who would do this, so I did (the link on that page was added later). My actual résumé is a good bit crazier.
I apologize for the use of _t in my types. I spend a lot of time at a level where I can do that; "reserved for system libraries? I am the system libraries".
Since people kept complaining, I've fixed the assignments of string literals to non-const char *s.
My use of type * name, however, is entirely intentional.
If you're using an older compiler, you might have trouble with the anonymous unions and the designated initializers - I think gcc 4.4 requires some extra braces to get them working together. Anything reasonably recent should work fine. Clang and gcc (newer than 4.4, at le

	var gulp = require('gulp'),
	sass = require('gulp-sass'),
	browserify = require('gulp-browserify'),
	concat = require('gulp-concat'),
	embedlr = require('gulp-embedlr'),
	refresh = require('gulp-livereload'),
	lrserver = require('tiny-lr')(),
	express = require('express'),
	livereload = require('connect-livereload')
	livereloadport = 35729,

	/**
	* Takes a Sails Model object (e.g. User) and a ValidationError object and translates it into a friendly
	* object for sending via JSON to client-side frameworks.
	*
	* To use add a new object on your model describing what validation errors should be translated:
	*
	* module.exports = {
	* attributes: {
	* name: {
	* type: 'string',

	ZIP,LAT,LNG
	00601,18.180555, -66.749961
	00602,18.361945, -67.175597
	00603,18.455183, -67.119887
	00606,18.158345, -66.932911
	00610,18.295366, -67.125135
	00612,18.402253, -66.711397
	00616,18.420412, -66.671979
	00617,18.445147, -66.559696
	00622,17.991245, -67.153993

	# UPD from 2018:
	# This gist was written for pre-1.0 version of Elixir and won't work on post-1.0 versions.
	# You probably consider using something else!

	defmodule SecureRandom do
	@moduledoc """
	Ruby-like SecureRandom module.

	## Examples