DrBoolean

const daggy = require('daggy')
const compose = (f, g) => x => f(g(x))
const id = x => x

//===============Define Coyoneda=========
const Coyoneda = daggy.tagged('x', 'f')

Coyoneda.prototype.map = function(f) {
  return Coyoneda(this.x, compose(f, this.f))
}

leonyu

These examples are presented in an attempt to show how each coding styles attempts to or does not attempt to isolate side-effects. There are only 2 semantic elements in a barebone "Hello World" implementation:

• Invocation of console.log
• Declaration of HELLO_WORLD

Since every coding style can abstract away data into a parameter or variable, there is no point for us to show that. All implementations assume HELLO_WORLD is a constant that is always inlined. This way it reduces the variations we need to present. (To make an anology, if we were to implement incrementByOne, would we need to inline the number 1 or pass it in as parameter?)

CAVEAT/LIMITATION: All implementations also assume console is static global. In case of functional programming, console.log is asumed to be a function that can be passed around without further modification. (This is not the case in the browser, but that can be resolved with console.log.bind(console))

Declarative

dherman

DOM selectors

var elements = query`.${className}`;

Localization

var message = l10n`Hello ${name}; you are visitor number ${visitor}:n!

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().

akalin

Direct links to Lecture Notes in Mathematics (Part 1)

*-Autonomous Categories - Michael Barr (1979) ([1], [2], [3], [4], [5], [6])

1-Dimensional Cohen-Macaulay Rings - Eben Matlis (1973) ([1], [2

shellkore

SQUASH

Whenever you want to squash last commits in a single commit:-

first check your log

git log

CASE 1: your head is at the commit in which you want others to be squashed

i-am-tom

const Task = require('data.task')

Task.prototype.alt = function (that) {
  return new Task((rej, res) =>
    this.fork(_ => that.fork(rej, res), res))
}

const hosts = [
  [ 'db1.mysite.com', 'user', 'password' ],
  [ 'db2.mysite.com', 'user', 'password' ],

dmitriz

const Task = require('data.task')

Task.prototype.alt = function (that) {
  return new Task((rej, res) =>
    this.fork(_ => that.fork(rej, res), res))
}

const hosts = [
  [ 'db1.mysite.com', 'user', 'password' ],
  [ 'db2.mysite.com', 'user', 'password' ],

dmitriz

High level style in javascript.

Opinions are like assholes, every one has got one.

This one is mine.

Punctuation: who cares?

Punctuation is a bikeshed. Put your semicolons, whitespace, and commas where you like them.

sukima

node_modules in git

December 10 2011
By mikeal

One of the many things we have been forced to rethink in the world of node is how we handle dependencies in applications.

One of the big changes that came with 0.4.0 was support for node_modules. This change had major consequences. It elevated local modules, in a local directory, above modules installed globally. Along with npm changing its default install preference to local rather than global we've seen a nearly unanimous shift to local module installs that has made global installs somewhat distasteful.