addyosmani

Yo.next stream of thought

We currently have an on-going design doc walking through our ideal implementation of Yeoman.next - a system of easily composable generators. Given the complexity of that task, we're likely going to need to break that proposal down into several sub-specs/tasks that we gradually introduce as generator system features. This gist is to mostly collect ideas that define how yo.next generators differ from what we have today.

The hope is that definitions will provide us some guidance when it comes to actually prototyping this system.

SlexAxton

gifify() {
  if [[ -n "$1" ]]; then
    if [[ $2 == '--good' ]]; then
      ffmpeg -i $1 -r 10 -vcodec png out-static-%05d.png
      time convert -verbose +dither -layers Optimize -resize 600x600\> out-static*.png  GIF:- | gifsicle --colors 128 --delay=5 --loop --optimize=3 --multifile - > $1.gif
      rm out-static*.png
    else
      ffmpeg -i $1 -s 600x400 -pix_fmt rgb24 -r 10 -f gif - | gifsicle --optimize=3 --delay=3 > $1.gif
    fi
  else

divanvisagie

var five = require( 'johnny-five' ),
    board,
    narf = require( 'narf' );
 
board = new five.Board();
 
/*
  Executes a command and fires event when done that
  will return the command output
*/

cookrn

Couldn't find the text of this for a while...

• Original (404'ed) -- https://plus.google.com/115094562986465477143/posts/Di6RwCNKCrf
• Fakeout -- http://www.dzone.com/links/rss/ryan_dahl_i_hate_almost_all_software.html
• Repost -- https://plus.google.com/116904230181415286707/posts/DnAMAN5sUR8

chriseppstein

@include handhelds {
  table.responsive {
    width: 100%;
    thead {
      display: none;
    }
    tr {
      display: block;
    }
    td, th {

remy

var dateUtil = function () {
  var monthDict = ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'];
  return {
    time: function (date) {
      var hour = date.getHours(),
          min = date.getMinutes() + "",
          ampm = 'AM';

      if (hour == 0) {
        hour = 12;

SBoudrias

bitwise=true boss=true browser=true debug=true eqeqeq=true eqnull=true es5=true esnext=true expr=true immed=true iterator=true lastsemic=true laxbreak=true laxcomma=true loopfunc=true maxlen=120 multistr=true newcap=true noarg=true onecase=true onevar=true plusplus=true proto=true regexdash=true regexp=true scripturl=true shadow=true smarttabs=true strict=true sub=true supernew=true undef=true validthis=true withstmt=true predef=["window","document"]

domenic

Here's how this works:

• Include a git_hooks/ directory in your project, with these two files (plus other hooks if you want, written in a similar style).
• Add "npm" to your devDependencies in package.json, so that the pre-commit hook can do its magic.
• Add test and lint scripts to your package.json, e.g.

    "scripts": {
        "test": "mocha",
 "lint": "jshint ./lib --show-non-errors"

ShirtlessKirk

/**
 * Luhn algorithm in JavaScript: validate credit card number supplied as string of numbers
 * @author ShirtlessKirk. Copyright (c) 2012.
 * @license WTFPL (http://www.wtfpl.net/txt/copying)
 */
var luhnChk = (function (arr) {
    return function (ccNum) {
        var 
            len = ccNum.length,
            bit = 1,

paulirish

// http://paulirish.com/2011/requestanimationframe-for-smart-animating/
// http://my.opera.com/emoller/blog/2011/12/20/requestanimationframe-for-smart-er-animating

// requestAnimationFrame polyfill by Erik Möller. fixes from Paul Irish and Tino Zijdel

// MIT license

(function() {
    var lastTime = 0;
    var vendors = ['ms', 'moz', 'webkit', 'o'];