azder

/**
 * @param array[] $data
 *
 * @return string
 *
 */
$csv = function ( array $data )
{

    $handle = fopen( 'php://temp', 'r+b' );

azder

//--
//-- FUNCTORS in ES6
//--


//-- BOILER PLATE

let fmap = (f) => (functor) => functor.map(f);
let c2   = (f2, f1) => (x) => f2(f1(x));
let c3   = (f3, f2, f1) => (x) => f3(f2(f1(x)));

azder

const R = require('ramda');

const drinkers = R.compose(
    R.map(({name, surname}) => `${name} ${surname} can drink!`),
    R.filter(({age}) => 21 < age)
);

const users = [
    {
        name:    'Kristijan',

azder

const isgen = (
    fn => fn instanceof Object.getPrototypeOf(function*(){}).constructor
);

azder

{
  // http://eslint.org/docs/rules/

  "ecmaFeatures": {
    "binaryLiterals": false,                    // enable binary literals
    "blockBindings": false,                     // enable let and const (aka block bindings)
    "defaultParams": false,                     // enable default function parameters
    "forOf": false,                             // enable for-of loops
    "generators": false,                        // enable generators
    "objectLiteralComputedProperties": false,   // enable computed object literal property names

azder

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

azder

<script src="bower-components/html2canvas/build/html2canvas.min.js"></script>
<style>
    #logo {
        width:     128px;
        height:    128px;
        font-size: 78px !important;
    }
</style>
<script>(function (w, $, canv) {

azder

function Foo(who) {
	this.me = who;
}

Foo.prototype.identify = function() {
	return "I am " + this.me;
};

function Bar(who) {
	Foo.call(this,"Bar:" + who);

azder

#include <assert.h>
#include <stdarg.h>
#include <stdbool.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>

enum type {
    NIL,

azder

    // for when you need Constructor
    const CF = fn => function (...args) {
        return fn.apply(this, ...args)
    };
    
    const CL = fn => class Klass {
        constructor(...args) {
            return fn.apply(this, ...args);
        }