Gabriel Dumitrescu gdumitrescu

Next-generation JavaScript frameworks

Web application frameworks have been developing fast in the past few years, and as the technologies that they're built on top of get more advanced, each of these frameworks is able to provide newer features to help developers build more complex applications. This year, we've seen the release of a new class of application frameworks that takes advantage of JavaScript's ability to be both on the client and the server. What this allows these frameworks to do is provide both a new level of abstraction by sharing code between client and server, as well as embrace the benefits of both client-side rendering and server-side rendering.

For the end user, they get smooth, desktop-like responsiveness from client-side rendering, while still being able to maintain the SEO and accessbility benefits of server-side rendering. For developers, that means writing less boilerplate code, and being able to focus more on writing the application logic.

Today, there are three main framew

Web Performance Power Tool: HTTP Archive (HAR) - blog post with video and details about the projects we covered.

The HAR Show GDL episode on YouTube

HAR Spec: http://www.softwareishard.com/blog/har-12-spec/
HTTP Archive (powered by HAR files): www.httparchive.org
HAR Viewer: http://code.google.com/p/harviewer/

by Dale Sande

CSS has had a long and sordid past. A developer never sets out with the goal of making a complete and total mess of things. Their intention is not to build something that is practically illegible, impractical to maintain and is limited in scale. But somehow, this is where many inevitably end up. Luckily, all is not lost. With some simple strategies, organizational methods and out-of-the box tools, we can really help get that junk-drawer inline.

For many of us getting started with Sass, at one time or another have created a junk-drawer of files. For most, this was a rookie mistake, but for others, this is a continuing issue with our architecture and file management techniques. Sass doesn't come with any real rules for file management so developers are pretty much left to their own devices.

Large CSS files and increased complexity

CSS started out with very simple intentions, but as [tableless web design][1.1] began to really take a foothold, o

Objects

To create a new object, use the new keyword followed by a call to a constructor function. Javascript provides the Object() constructor out-of-the-box:

var toilet = new Object();

Properties

Once you have an object, you can set and get properties on it, like this:

	@mixin mobile_bg($file){
	background-image: image-url('mobile/standard/#{$file}');

	@media screen and (-webkit-min-device-pixel-ratio: 2) {
	background-image: image-url('mobile/retina/#{$file}');
	background-size: image-width('mobile/standard/#{$file}') image-height('mobile/standard/#{$file}');
	}
	}

	// Usage

	#!/bin/bash

	cur=`pwd`

	inotifywait -mqr --timefmt '%d/%m/%y %H:%M' --format '%T %w %f' \
	-e modify ./ \| while read date time dir file; do
	ext="${file##*.}"
	if [[ "$ext" = "go" ]]; then
	echo "$file changed @ $time $date, rebuilding..."
	go build

	var fs = require('fs');
	var lame = require('lame');
	var Speaker = require('speaker');

	fs.createReadStream(process.argv[2])
	.pipe(new lame.Decoder())
	.on('format', function (format) {
	this.pipe(new Speaker(format));
	});

	# = require '../components/jquery/jquery'
	# = require '../components/angular-complete/angular'



	Controllers = angular.module 'controllers', []

	Controllers.controller 'PhoneListCtrl', ['$scope', ($scope)->
	$scope.phones = [
	{name: "Nexus S", snippet: "Fast just got faster with Nexus S."},

	guard 'process', :name => 'minify-screen-js', :command => 'juicer merge js/all.js -o js/all.min.js --force -s' do
	watch /^js\/brianregan\/screen.js/
	end

	guard 'process', :name => 'shrink-images', :command => 'ruby resize-mobile-images.rb mobileretina' do
	watch /^images\/mobileretina\/.+/
	end