nkt

wrk -t4 -c400 -d10s http://127.0.0.1:1337/

PHP

Running 10s test @ http://127.0.0.1:1337/
  4 threads and 400 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
 Latency 7.02ms 6.94ms 82.86ms 85.27%

adewale

{
  "statements": [
    {
      "source": {
        "web": {
          "site": "https://applinkingexperiment.appspot.com."
        }
      },
      "relation": "delegate_permission/common.handle_all_urls",
      "target": {

xjamundx

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

oshliaer

###Batch import CSV to a Spreadsheet http://stackoverflow.com/questions/17578317

h2non

var fs = require('fs')
var pipefy = require('pipefy')
var AWS = require('aws-sdk')
var s3 = new AWS.S3()

// Keep safe the original function with proper scope
var putObject = s3.putObject.bind(s3)

// Override the function
s3.putObject = function (opts, cb) {

masahirompp

/// <reference path="../tsd/tsd.d.ts" />

import mongoose = require('mongoose');
import passport = require('passport');

interface IUser extends mongoose.Document {
  provider: string;
  id: string;
  authorId: string;
  displayName: string;

curtismcmullan

#!/bin/bash

# Following the guide found at this page
# http://programmingarehard.com/2014/03/17/behat-and-selenium-in-vagrant.html

echo "\r\nUpdating system ...\r\n"
sudo apt-get update


# Create folder to place selenium in

azam

convert -density 256x256 -background transparent favicon.svg -define icon:auto-resize -colors 256 favicon.ico

rodneyrehm

some tools for diagrams in software documentation

Diagrams For Documentation

Obvious Choices

• Graphviz
• Pandoc

ASCII

machinaut

<?xml version='1.0' encoding='ASCII'?>
<flow_graph>
  <timestamp>Tue Aug 12 14:13:51 2014</timestamp>
  <block>
    <key>options</key>
    <param>
      <key>id</key>
      <value>fm_receiver</value>
    </param>
    <param>