Kevin Lozandier lozandier

Re: http://blog.chromium.org/2015/03/new-javascript-techniques-for-rapid.html

V8 Optimisations to enable fast page startup

As mentioned in our Chromium blog post, Chrome 41 introduces support for streaming parsing of JavaScript files using the async or defer attributes. This is where the V8 parser will parse any incoming JavaScript piece-by-piece so the compiler can immediately begin compiling the AST when script loading has completed. This lets us do something useful while waiting for the page to load. Compare:

This means parsing can be removed from the critical path when loading up the page. In these cases such scripts are parsed on a separate thread as soon as the download begins, allowing parsing to complete very soon after the download has completed (milliseconds), leading to pages (potentially) loading much faster.

CSS Layout Debugger

A tweet-sized debugger for visualizing your CSS layouts. Outlines every DOM element on your page a random (valid) CSS hex color.

One-line version to paste in your DevTools

Use $$ if your browser aliases it:

~ 108 byte version

[UIScreen mainScreen].bounds.size.height reports the following sizes, in points, for these iOS devices:

iPad Air/Mini/etc. (some require @2x assets)

Height: 1024
Width: 768

iPhone 6 Plus (401ppi display requires @3x assets)

Height: 736

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.

Deprecated. See https://www.polymer-project.org/articles/unit-testing-elements.html for the latest version.

Unit Testing Polymer Elements

Note: this guide is a work-in-progress and will be added to the Polymer docs when it's ready. We have updated <seed-element> to include unit tests and this guide has been moved to Google docs. Expect a version on the Polymer site before the end of September.

After spending days working on your <super-awesome> Polymer element, you’re finally ready to share it with the rest of the world. You add the code for using it to your demo, iterate on it over time and come back to it one day when..uh oh. The demo broke because something has gone horribly wrong. Suddenly, <super-awesome> isn’t starting to look so great. Now you’re stuck trying to backtrack through your commit log to figure out how you broke the code. You’re not going to have a fun time.

If you’ve been working on the front-end for a while, even if you haven’t really played with Polymer elements before, this s

Setting up Ruby, Rails, Nginx, Passenger, PostgreSQL 9 on Ubuntu 12.04 LTS for Windows Azure

Last updated: 12/31/2013

Fix the locale issue

Edit /etc/default/locale as sudo.
Append LC_ALL="en_US.UTF-8" at the end of the file, save and quit.
sudo locale-gen en_US en_US.UTF-8
sudo dpkg-reconfigure locales

	.body
	.columnA
	A
	.columnB
	B
	.columnC
	C

	var http = require("http");
	var ASQ = require("asynquence-contrib"); // bring in ASQ + optional contrib plugins

	var server = http.createServer();
	server.listen(8000);

	ASQ.react(function(next){
	server.on("request",next);
	})
	.runner(function*(channel){

	// --------------------------------------------------------------------------------------
	// A More Modern Scale for Web Typography
	// Based on this article: http://typecast.com/blog/a-more-modern-scale-for-web-typography
	// --------------------------------------------------------------------------------------

	$body-font-size: 1em !default;

	// Adjusts body typography to be default
	// for each browser.
	@mixin reset-body-font-size($font-size: 100%, $size-adjustment: 0.5) {