ericelliott

Two Simple Changes to Simplify class

I'm not suggesting drastic action. I don't want to break backwards compatibility. I simply want to make the class feature more usable to a broader cross section of the community. I believe there is some low-hanging fruit that can be harvested to that end.

Imagine AutoMaker contained class Car, but the author wants to take advantage of prototypes to enable factory polymorphism in order to dynamically swap out implementation.

Stampit does something similar to this in order to supply information needed to inherit from composable factory functions, known as stamps.

This isn't the only way to achieve this, but it is a convenient way which is compatible with .call(), .apply(), and .bind().

GlynnPhillips

#!/usr/bin/env node

var program = require('commander');
var request = require('request');
var chalk = require('chalk');

program
	.version('0.0.1')
	.usage('[options] <keywords>')
	.option('-o, --owner [name]', 'Filter by the repositories owner')

developit

An Alias to run Chrome with tracing enabled

For Chrome Canary:

alias hydra='/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --no-sandbox --js-flags="--user-data-dir=/tmp/profile --trace-hydrogen --trace-phase=Z --trace-deopt --code-comments --hydrogen-track-positions --redirect-code-traces"'

For regular ol' Chrome:

jkrems

In all the discussions about ES6 one thing is bugging me. I'm picking one random comment here from this io.js issue but it's something that comes up over and over again:

There's sentiment from one group that Node should have full support for Promises. While at the same time another group wants generator syntax support (e.g. var f = yield fs.stat(...)).

People keep putting generators, callbacks, co, thunks, control flow libraries, and promises into one bucket. If you read that list and you think "well, they are all kind of doing the same thing", then this is to you.

hyle

// knockout 3.3.0

ko.utils.addOrRemoveItem                        = function (array, value, included) { /* .. */ }

ko.utils.anyDomNodeIsAttachedToDocument         = function (nodes) { /* .. */ }

ko.utils.arrayFilter                            = function (array, predicate) { /* .. */ }

ko.utils.arrayFirst                             = function (array, predicate, predicateOwner) { /* .. */ }

vybs

<div class="guided-edit">
  {>_close_action/}
  {<closeText}{i18n_text_plain__close}{/closeText}
  {?firstTaskTitleString}
    <h1>{firstTaskTitleString|s}</h1>
  {/firstTaskTitleString}
  
  <form class="standard-form" id="{name}_id" name="{name}" method="{method}" action="{action}">
    <fieldset>
      <legend>{i18n_text_plain__what_is_your_industry}</legend>

anthonyshort

@mixin border-radius($radius, $prefixes: -moz -webkit -o) {
	@each $prefix in $prefixes {
		#{$prefix}-border-radius:$radius;
	}
	
	border-radius:$radius;
}

#id {
	@include border-radius(5px, -moz -webkit);

indutny

'use strict';

// Quiz:
//
// Implement `solution` function using only calls to API methods below and no
// other JS primitives (even math).
//
// Correct implementation will print "Success!" once executed
//

addyosmani

Composition

On an architectural level, the way we craft large-scale applications in JavaScript has changed in at least one fundamental way in the last four years. Once you remove the minutia of machinery bringing forth data-binding, immutable data-structures and virtual-DOM (all of which are interesting problem spaces) the one key concept that many devs seem to have organically converged on is composition. Composition is incredibly powerful, allowing us to stitch together reusable pieces of functionality to "compose" a larger application. Composition eschews in a mindset of things being good when they're modular, smaller and easier to test. Easier to reason with. Easier to distribute. Heck, just look at how well that works for Node.

Composition is one of the reasons we regularly talk about React "Components", "Ember.Component"s, Angular directives, Polymer elements and of course, straight-up Web Components. We may argue about the frameworks and libraries surrounding t

gbabula

"scripts": {
  "serve": "http-server -p 9966",
  "start": "npm run serve & npm run build",
  "start-dev": "npm run serve & npm run watch",
  "build-js": "browserify -u bootstrap -u jquery -u lodash -u isomorphic-fetch src/scripts/g5-component.js --s 'g5-component' | uglifyjs -mc drop_console > src/static/g5-component.js",
  "build-js-vendor": "browserify -r bootstrap -r jquery -r lodash -r isomorphic-fetch | uglifyjs -mc > src/static/g5-component-vendor.js",
  "build-js-full": "browserify src/scripts/g5-component.js --s 'g5-component' | uglifyjs -mc drop_console > src/static/g5-component.js",
  "build-css": "lessc src/styles/component.less > src/static/bundle.css",
  "build": "npm run build-js",
  "watch-js": "watchify -u bootstrap -u jquery -u lodash -u isomorphic-fetch src/scripts/g5-component.js --s 'g5-component' -o src/static/g5-component.js -dv",