Models | Examples |
---|---|
Display ads | Yahoo! |
Search ads |
<script> | |
(function(){ | |
// Look for a jqversion query parameter and grab any following version. | |
// Limit to digits and letters to prevent any XSS attempts | |
var verMatch = /jqversion=([\w\.]+)/.exec( location.search ), | |
// our matched version, e.g., 1.6.4 or 1.7rc1 | |
version = verMatch && verMatch[1], | |
src; | |
if ( version ) { | |
// version was specified, use jQuery's CDN to acccess non-mininfied betas and RCs |
AngularJS — Superheroic JavaScript MVW Framework - http://angularjs.org/
Ключевое отличие AngularJS от Knockout / Хабрахабр - http://habrahabr.ru/post/165275/
Building Huuuuuge Apps with AngularJS - Brian Ford - http://briantford.com/blog/huuuuuge-angular-apps.html
AngularJS. Developer Guide. Overview - http://docs.angularjs.org/guide/overview
IE6 Only | |
================== | |
_selector {...} | |
IE6 & IE7 | |
================== | |
*html or { _property: } | |
IE7 Only | |
================== |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
-
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the
secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection. -
Use production SSL certificates locally. This is annoying
// Just before switching jobs: | |
// Add one of these. | |
// Preferably into the same commit where you do a large merge. | |
// | |
// This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
// and then it quickly escalated into more and more evil suggestions. | |
// I've tried to capture interesting suggestions here. | |
// | |
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
Google Chrome Developers says:
The new WOFF 2.0 Web Font compression format offers a 30% average gain over WOFF 1.0 (up to 50%+ in some cases). WOFF 2.0 is available since Chrome 36 and Opera 23.
Some examples of file size differences: WOFF vs. WOFF2
/* ******************************************************************************************* | |
* THE UPDATED VERSION IS AVAILABLE AT | |
* https://github.com/LeCoupa/awesome-cheatsheets | |
* ******************************************************************************************* */ | |
// 0. Synopsis. | |
// http://nodejs.org/api/synopsis.html |
(by @andrestaltz)
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.