Nikos Gereoudakis stream7

The idea:

allow precompilation which outputs a set of compiled cache-busted files and produces a mapping object { source_path => compiled name }
make this mapping available to the production code through the environment variable (good for Heroku)
still support on-the-fly compilation for the development machine

asset-compilers.coffee is a adapter module around connect-assets and the "mapping" JSON. Also adds 2 custom compilers - a thin Sass wrapper around the official gem and a Jade compiler for client-side templates

build_assets.coffee is a CLI script using the previous module to perform the compilation and outputs the mapping JSON to a file. It also directly copies all the assets that do not need compilation

config.coffee is an example how STATIC_HOST is made available for the application

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

Get Out Of Photoshop

The Post PSD Era: http://bradfrostweb.com/blog/post/the-post-psd-era/
Mocking Up is Hard To Do: http://blog.bearded.com/post/21447195970/mocking-up-is-hard-to-do

Atomic Design

An extract from Designing Atoms and Elements: http://stuffandnonsense.co.uk/blog/about/an-extract-from-designing-atoms-and-elements
- Smashing Book #3 from where it came: https://shop.smashingmagazine.com/smashing-book-3.html
Atomic Web Design: http://bradfrostweb.com/blog/post/atomic-web-design/

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

Go HTTP standalone (as the control group)
Nginx proxy to Go HTTP
Nginx fastcgi to Go TCP FastCGI
Nginx fastcgi to Go Unix Socket FastCGI

List of JavaScript Build Tools

Yet another framework syndrome

Name	Date	URL	Stars
Jake	April 2010	https://github.com/mde/jake	1000
Brunch	January 2011	http://brunch.io/	3882
~~smoosh~~	~~March 2011~~	~~https://github.com/fat/smoosh~~	~~329~~
~~anvil.js~~	~~February 2012~~	~~https://github.com/anviljs/anvil.js~~	~~161~~

	gifify() {
	if [[ -n "$1" ]]; then
	if [[ $2 == '--good' ]]; then
	ffmpeg -i $1 -r 10 -vcodec png out-static-%05d.png
	time convert -verbose +dither -layers Optimize -resize 600x600\> out-static*.png GIF:- \| gifsicle --colors 128 --delay=5 --loop --optimize=3 --multifile - > $1.gif
	rm out-static*.png
	else
	ffmpeg -i $1 -s 600x400 -pix_fmt rgb24 -r 10 -f gif - \| gifsicle --optimize=3 --delay=3 > $1.gif
	fi
	else

	$ = jQuery

	queues = {}
	running = false

	queue = (name) ->
	name = 'default' if name is true
	queues[name] or= []

	next = (name) ->

	Ruby 2.1.0 in Production: known bugs and patches

	Last week, we upgraded the github.com rails app to ruby 2.1.0 in production.
	While testing the new build for rollout, we ran into a number of bugs. Most of
	these have been fixed on trunk already, but I've documented them below to help
	anyone else who might be testing ruby 2.1 in production.

	@naruse I think we should backport these patches to the ruby_2_1 branch and
	release 2.1.1 sooner rather than later, as some of the bugs are quite critical.
	I'm happy to offer any assistance I can to expedite this process.

	À A
	Á A
	Â A
	Ã A
	Ä A
	Å A
	Æ A
	à a
	á a
	â a

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048