vasilisvg

#Retina images Sharpness is relative. We can only observe if something is really sharp if we can see it next to something that's sharper. Lots of people are looking for solutions for the problem that images look blurry on retina displays. All solutions I've seen so far give the advice to send an image that's twice as wide and twice as high to these new screens. Before you start sending these images, be sure to understand that these files will be four times the size of the smaller version. People with a high end device and a low end connection—everybody in the train in The Netherlands—will hate you.

##Image types I'm generalizing here, but there are two types of images: (1) graphics like logos and (2) photos. Quadroupled images might be justified for the first kind, for logos, icons, things like that. You could also try to find a solution in clever SVG files—with media queries in them, why not? These kinds of ima

paulirish

Open Conference Expectations

This document lays out some baseline expectations between conference speakers and conference presenters. The general goal is to maximize the value the conference provides to its attendees and community and to let speakers know what they might reasonably expect from a conference.

We believe that all speakers should reasonably expect these things, not just speakers who are known to draw large crowds, because no one is a rockstar but more people should have the chance to be one. We believe that conferences are better -- and, dare we say, more diverse -- when the people speaking are not just the people who can afford to get themselves there, either because their company paid or they foot the bill themselves. Basically, this isn't a rock show rider, it's some ideas that should help get the voices of lesser known folks heard.

These expectations should serve as a starting point for discussion between speaker and organizer. They are not a list of demands; they are a list of rea

necolas

• Avoid reprocessing the same block in different HTML files.
• Throw warning when processing a different block to an existing destination file. Hashing will avoid collisions, but introduce confusion.
• Add file versioning for inline media and CSS images.
• Avoid need for 'usemin' task - get the replacement element pattern from the first/last HTML element in actual block being replaced. Added benefit of preserving other attributes that may exist (e.g. title, media).

Acknowledgements: This is an adaption of some of Mickael Daniel's work on h5bp/node-build-script

harthur

Go to Sublime Text 2 > Preferences > Key Bindings - User and add this JSON to the file:

[
    { "keys": ["super+shift+l"],
      "command": "insert_snippet",
      "args": {
        "contents": "console.log(${1:}$SELECTION);${0}"
      }
 }

czottmann

eirikbacker

//addEventListener polyfill 1.0 / Eirik Backer / MIT Licence
(function(win, doc){
	if(win.addEventListener)return;		//No need to polyfill

	function docHijack(p){var old = doc[p];doc[p] = function(v){return addListen(old(v))}}
	function addEvent(on, fn, self){
		return (self = this).attachEvent('on' + on, function(e){
			var e = e || win.event;
			e.preventDefault  = e.preventDefault  || function(){e.returnValue = false}
			e.stopPropagation = e.stopPropagation || function(){e.cancelBubble = true}

TooTallNate

Why is Node async?

• Asynchronous code is how you write low-resource, high-concurrency servers. See http://www.kegel.com/c10k.html.
• Node embracing async from the get-go means that servers are low-resource, high-concurrency by default.
• Async + JavaScript = Perfect fit for an event loop.
• When it comes to threads vs event-loop, there are times when either are advantageous.
  • But there are things very hard or impossible to do with threads.
  • WebSockets are difficult to do properly with threads. That's one example where non-blocking IO (async) has a major advantage.
  • RAM usage is another factor, especially when we're talking about the physical hardware required to run your application, which translates to real dollars.
• It depends on your application in the end:

kulor

var async = require('async'); // npm install async
async.parallel({
    foo: function(callback){
        http.get({host:'localhost', port:9999, path:'/foo'}, function (res) {
            res.on('data', function (data) {
                callback(null, JSON.parse(data.toString()));
            });
        })
    },
    bar: function(callback){

willkg

Below find the "reverse recruit" template. I'm using it. So can you!

===

Hi!

I'm not currently looking for a job as I'm pretty happy at my current job.

However Mozilla is hiring into a variety of positions. Mozilla also has

balupton

# Fix Github Pages
# Usage: fgp YOUR-GITHUB-PROJECTS-SSH-REPO-URL
function fgp {
	git clone $1 fixit
	cd fixit
	git checkout gh-pages
	git push origin :gh-pages
	git push origin --all
	cd ..
	rm -Rf fixit