Picking the right architecture = Picking the right battles + Managing trade-offs
| var Index = React.createClass({ | |
| getInitialState: function () { | |
| return { | |
| lastPress: 0 | |
| } | |
| }, | |
| onPress: function () { | |
| var delta = new Date().getTime() - this.state.lastPress; |
| let isFunction = function(obj) { | |
| return typeof obj == 'function' || false; | |
| }; | |
| class EventEmitter { | |
| constructor() { | |
| this.listeners = new Map(); | |
| } | |
| addListener(label, callback) { | |
| this.listeners.has(label) || this.listeners.set(label, []); |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| /** | |
| * ================== angular-ios9-uiwebview.patch.js v1.1.1 ================== | |
| * | |
| * This patch works around iOS9 UIWebView regression that causes infinite digest | |
| * errors in Angular. | |
| * | |
| * The patch can be applied to Angular 1.2.0 – 1.4.5. Newer versions of Angular | |
| * have the workaround baked in. | |
| * | |
| * To apply this patch load/bundle this file with your application and add a |
| import express from "express"; | |
| /** | |
| * Takes a route handling function and returns a function | |
| * that wraps it after first checking that the strings in | |
| * `reserved` are not part of `req.body`. Used for ensuring | |
| * create and update requests do not overwrite server-generated | |
| * values. | |
| */ | |
| function checkReservedParams(routeHandler, ...reserved) { |
I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.
In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.
While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.
Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio
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.
The final result: require() any module on npm in your browser console with browserify
This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.
Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5
These rules are adopted from the AngularJS commit conventions.
