mathiasbynens

Looking for support tables for HTML/CSS/JavaScript features or details on their implementation status in major browsers?

• Chrome Platform Status (covers Chromium and thus includes Opera)
• Firefox Platform Status
• Microsoft Edge Platform Status
• WebKit Feature Status
• API Catalog

And then there’s Can I use…?.

trevnorris

While the standard 80 character limit for source code can be traced back to the
IBM punch card[1] it can still be seen as a good upper bound for how long lines
of text should be on modern high definition displays.

First thing we must acknowledge is that source code is not read in the
traditional sense. Instead developers scan the source using non-linear eye
movements[2] or stay fixated in a small area of code while working out the
logical details of code being written. The fixation on a single location, even
for more than a few seconds, leads to a loss of visual accuity. Which occurs
when the eyes do not perform frequent saccadic eye movements.[3] Further

Avinash-Raj

#!/usr/bin/env python
# Here is the python2 script to see  StackOverflow 2015 election candidates who're going to the next phase along with their vote-counts.
# For this script to work, you must need to install Python's BeautifulSoup html parser.
# Created by Stack Overflow user Avinash Raj ( http://stackoverflow.com/users/3297613/avinash-raj )


from bs4 import BeautifulSoup
import urllib2
s = urllib2.urlopen('http://stackoverflow.com/election/6?tab=primary')
soup = BeautifulSoup(s)

rvagg

#!/bin/bash

# Note your /usr/local will need to be writable by the user running it,
# alternatively run it with `sudo`

hasxz=$(which xzcat)
os=$(uname | tr '[A-Z]' '[a-z]')
arch=$(uname -m)
targetdir="/usr/local/"
domain=nodejs.org

staltz

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.

---

matthewhudson

A good commit message looks like this:

Header line: explaining the commit in one line

Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc etc.

The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about