jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"

mugifly

'use strict';

angular.module('foo', [])

.filter('substring', function() {
	return function(str, start, end) {
		return str.substring(start, end);
	};
})

petehamilton

Dashboards

• Team Dashboard - http://fdietz.github.io/team_dashboard/
• Geckoboard - http://www.geckoboard.com/ - Slick data dashboards.
• Leftronic - https://www.leftronic.com/ - Similar, doesn't seem quite as organised looking
• Dashing - http://shopify.github.io/dashing/ - Simple metric dashboards by Shopify. Widget list

Charting

• HighCharts - http://www.highcharts.com/ Not very inspiring but very widely used & performant
• Google Charts - https://developers.google.com/chart/ Again, not very inspiring but can be customised
• Flot - http://www.flotcharts.org/ Gorgeous slick HTML5 graphs

nodesocket

/* Flatten das boostrap */
.well, .navbar-inner, .popover, .btn, .tooltip, input, select, textarea, pre, .progress, .modal, .add-on, .alert, .table-bordered, .nav>.active>a, .dropdown-menu, .tooltip-inner, .badge, .label, .img-polaroid {
 	-moz-box-shadow: none !important;
	-webkit-box-shadow: none !important;
	box-shadow: none !important;
	-webkit-border-radius: 0px !important;
	-moz-border-radius: 0px !important;
	border-radius: 0px !important;
	border-collapse: collapse !important;
	background-image: none !important;

PaulKinlan

(function() { 
  var CSSCriticalPath = function(w, d, opts) {
    var opt = opts || {};
    var css = {};
    var pushCSS = function(r) {
      if(!!css[r.selectorText] === false) css[r.selectorText] = {};
      var styles = r.style.cssText.split(/;(?![A-Za-z0-9])/);
      for(var i = 0; i < styles.length; i++) {
        if(!!styles[i] === false) continue;
        var pair = styles[i].split(": ");

antirez

/* vmlatency.c
 *
 * Measure max latency of a running process that does not result from
 * syscalls. Basically this software should provide an hint about how much
 * time the kernel leaves the process without a chance to run.
 *
 * Copyright (C) 2014 Salvatore Sanfilippo.
 * This software is released under the BSD two-clause license.
 *
 * compile with: cc vmlatency.c -o vmlatency

octocat

# Compiled source #
###################
*.com
*.class
*.dll
*.exe
*.o
*.so

# Packages #

ellemenno

#!/usr/bin/env ruby
# encoding: UTF-8


@dot_cycle = ['⣾','⣽','⣻','⢿','⡿','⣟','⣯','⣷']
#braille random: 0x2800 - 0x28ff

@z_arrow = ['←','↖','↑','↗','→','↘','↓','↙']
@z_b   = ['b','ᓂ','q','ᓄ']
@z_d   = ['d','ᓇ','p','ᓀ']

igrigorik

Navigation and Resource Timing provides timing data for the fetch, but currently there is no interoperable way for the server to communicate own timing information to the client. For example:

• What steps were taken to generate the resource, and how long each took. Many sites already embed this type of information via HTML comments - e.g. wordpress emits <!--Page generated in X.X seconds.--> , and many sites provide more detailed stats (cache, db, generation) to enable performance debugging.
• If proxied, where was the time spent - e.g. time to fetch from origin, time to process response, etc.

Instead of relying on arbitrary HTML comments, we can define an HTTP header that can be used to send key-value pairs in a well defined format. Making this data available via a well defined interface would...

• Allow UA and other developer tools to automatically annotate appropriate timelines.
• Allow analytics vendors to gather this data for operational analysis.
• Allows proxies and CDNs to append custom timing d

danielgtaylor

Moving to ES6 from CoffeeScript

I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.

In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.

While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.

Punctuation

Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio