Mehrdad Shokri mehrdad-shokri

Business Models

Advertising

Models	Examples
Display ads	Yahoo!
Search ads	Google

⇐ back to the gist-blog at jrw.fi

Advanced SCSS

Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.

I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.

This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso

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.

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

	This is gist.
	There are many like it, but this one is mine.
	It is my life.
	I must master it as I must master my life.
	Without me gist is useless.
	Without gist, I am useless.


	#
	# Slightly tighter CORS config for nginx
	#
	# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
	#
	# Despite the W3C guidance suggesting that a list of origins can be passed as part of
	# Access-Control-Allow-Origin headers, several browsers (well, at least Firefox)
	# don't seem to play nicely with this.
	#

	#
	# Acts as a nginx HTTPS proxy server
	# enabling CORS only to domains matched by regex
	# /https?://.*\.mckinsey\.com(:[0-9]+)?)/
	#
	# Based on:
	# * http://blog.themillhousegroup.com/2013/05/nginx-as-cors-enabled-https-proxy.html
	# * http://enable-cors.org/server_nginx.html
	#
	server {

	#
	# CORS header support
	#
	# One way to use this is by placing it into a file called "cors_support"
	# under your Nginx configuration directory and placing the following
	# statement inside your location block(s):
	#
	# include cors_support;
	#
	# As of Nginx 1.7.5, add_header supports an "always" parameter which

	// === Arrays

	var [a, b] = [1, 2];
	console.log(a, b);
	//=> 1 2


	// Use from functions, only select from pattern
	var foo = () => [1, 2, 3];