charlespwd

#!/usr/bin/env bash
set -eou pipefail

profile=$1
frameRate=${2:-10}
timeline='timeline.json'
cat $profile \
  | jq '.[] | select(.args.snapshot | . and (type == "string") and contains("/9j"))' \
  | jq -s . \
  > $timeline

siddharthkp

This proposal is not longer active. Context: https://twitter.com/siddharthkp/status/909818777314902016

---

ianmcnally

const { parse } = require('css')
const { readdirSync, readFileSync } = require('fs')
const { basename, extname, resolve } = require('path')
const camel = require('lodash.camelcase')

const baseNameForCSSFile = filename => basename(filename, '.css')

const isAClassSelector = selector => /^\./.test(selector)

const removeLeadingDotAndTrailingSelectors = selector =>

stekhn

var elastic = require('elasticsearch');

var client = new elastic.Client({ host: 'localhost:9200' });
var index = 'myindex';
var type = 'document';

(function init() {

  Promise.resolve()
    .then(deleteIndex, handleError)

rauchg

Minimum Viable Async with Node 6

With the release of Node 6.0.0, the surface of code that needs transpilation to use ES6 features has been reduced very dramatically.

This is what my current workflow looks like to set up a minimalistic and fast microservice using micro and async + await.

The promise

gaearon

// connect() is a function that injects Redux-related props into your component.
// You can inject data and callbacks that change that data by dispatching actions.
function connect(mapStateToProps, mapDispatchToProps) {
  // It lets us inject component as the last step so people can use it as a decorator.
  // Generally you don't need to worry about it.
  return function (WrappedComponent) {
    // It returns a component
    return class extends React.Component {
      render() {
        return (

kaleksandrov

#!/bin/bash

case $# in
   0)
      echo "Usage: $0 {start|stop}"
      exit 1
      ;;
   1)
      case $1 in
         start)

larahogan

Native app performance metrics

This is a draft list of what we're thinking about measuring in Etsy's native apps.

Currently we're looking at how to measure these things with Espresso and Kif (or if each metric is even possible to measure in an automated way). We'd like to build internal dashboards and alerts around regressions in these metrics using automated tests. In the future, we'll want to measure most of these things with RUM too.

Overall app metrics

• App launch time - how long does it take between tapping the icon and being able to interact with the app?
• Time to complete critical flows - using automated testing, how long does it take a user to finish the checkout flow, etc.?
• Battery usage, including radio usage and GPS usage
• Peak memory allocation