gaearon

function mapValues(obj, fn) {
  return Object.keys(obj).reduce((result, key) => {
    result[key] = fn(obj[key], key);
    return result;
  }, {});
}

function pick(obj, fn) {
  return Object.keys(obj).reduce((result, key) => {
    if (fn(obj[key])) {

rgbkrk

The Jupyter and IPython projects have been around more than 10 years and a lot has changed over the years in terms of frontend development: V8, Node, npm, transpilers, JS Compilers, competing module loading systems, auto-updating browsers, new frameworks, and many other bits. They've all come and made front end development much better. At the same time, they've bred complexity in choice and decisions. Some of the biggest warts have been the document API for the DOM, how we work on it, the tendency to get addicted to the ease of jQuery, and the resulting jQuery soup that gets created. Large projects have to make a choice on how they're going to package and ship components of their overall application.

There was a time at which I was comfortable in CoffeeScript. Now that I've read JavaScript the Good Parts, Node.js the Right Way, read and written [more](https://github.com/nteract/jupyter-sideca

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.

justinwoo

Reposted from Qiita

For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.

Why I'm tired of using and teaching flux

There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.

If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:

kenperkins

We’re looking for a full-stack developer ready to help us build the next platform for Developer Experience at Rackspace. We need a leader to drive engineering decisions for the front and back-end, as well as implement significant portions of our Developer Portal. Working effectively as a remote employee in a collaborative environment, especially on open-source software, is an absolute must-have skill.

The Developer Experience team is focused on making the end-to-end experience for developers on the Rackspace Cloud awesome. From community & outreach to docs, tools & SDKs, our team is on the front lines for engaging with developers who are building modern cloud applications.

Ideal candidates should have experience with contemporary front-end frameworks, including but not limited to Ember, React, Angular and Backbone. Additionally, candidates should have experience with back-end frameworks for building modern web applications. Representative examples might include Python a

etoews

#!/bin/bash

set -o errexit

# This script assumes you're running it initially as root and you've created it with a key pair. If you
# haven't, you'll be locked out of your server.

if [ -z "$1" ]; then
  echo "Usage: $0 NON_ROOT_USER"
  echo "Example: $0 foo"

ogrisel

#!/usr/bin/env python
import dill
import sys


payload_filename = sys.argv[1]

if len(sys.argv) > 2:
    print('Restoring __main__ context')
    main_filename = sys.argv[2]

kachayev

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

arfon

###Title

Academic publishing using Git and GitHub

###Additional faciliators

Jessica Lord
Chrissie Brodigan
Andrew Nesbitt
Karthik Ram

jbarratt

#!/usr/bin/env python

""" A cross-platform (POSIX, at least) tool to list running IPython Notebooks
    and their working directories.

    This code will be incredibly simpler to write as of IPython 3.0, so
    contains numerous workarounds to make it work on 2.x.

    Thanks to @takluyver for the suggestions for improvement.