| $ brew install bash-completion | |
| ==> Downloading http://bash-completion.alioth.debian.org/files/bash-completion-1.3.tar.bz2 | |
| ######################################################################## 100.0% | |
| ==> ./configure --prefix=/usr/local/Cellar/bash-completion/1.3 | |
| ==> make install | |
| ==> Caveats | |
| Add the following lines to your ~/.bash_profile file: | |
| if [ -f `brew --prefix`/etc/bash_completion ]; then | |
| . `brew --prefix`/etc/bash_completion | |
| fi |
| // https://github.com/deebloo/rxjs-worker | |
| var observable = Observable.of([0, 1, 2, 3, 4]); | |
| observable | |
| .map(function (data) { | |
| return data.concat([5, 6, 7, 8, 9]); | |
| }) | |
| .workerMap(function (data) { | |
| return data.concat([10,11,12,13,14]);; | |
| }) |
| // All webpack chunks have an identifier that is written to both the chunk and | |
| // the chunk manifest. | |
| // | |
| // By default, webpack uses "int" identifiers, where the identifiers are | |
| // sequentially generated after chunks are ordered by OccurenceOrderPlugin. | |
| // | |
| // The result of this is that small code changes may cause chunks to be | |
| // reordered, leading to a cascading change of chunk ids, and a large number of | |
| // chunk rehashes that could have been avoided. | |
| // |
git clone https://github.com/ajaxorg/cloud9.git
git submodule update --init --recursive
git apply cloud9.patch
git clone git://github.com/semu/connect-basic-auth.git support/connect-basic-auth
node bin/cloud9.js -c config.js
Open the url http://127.0.0.1:3000/ when prompt the authorization,username is "username" and password is "password".
Redux has brought the notion of reducer back into the awareness of many developers for whom they are a novel concept. In fact they are quite simple, and used all the time in such things as SUM aggregations in databases, where they compute a single value from many.
It's great that Redux has made reducers known to a broader audience, though they are relatively ancient concepts in programming, in fact. But the particular way Redux illustrates a reducer in its documentaion is, in my opinion, with a coding style that is harder to extend and read than it should be. Let's distill reducers down to their essensce, and build up Redux reducers in a way that lowers complexity, and helps separate Redux idioms from your business logic.
A reducer is a pure function that accepts more arguments than it returns. That is to say - one whose "arity" is greater than 1. It 'reduces' the two things you pass it down to a single value. Here are two reducers, in a map
| /* | |
| * This is just an experiment. Don't read too much into the fact that these are global variables. | |
| * The basic idea is to combine the two steps of defining a constructor and modifying a prototype | |
| * into just one function call that looks more like traditional classes and other OO languages. | |
| */ | |
| // Utility function | |
| function mixin(receiver, supplier) { | |
| if (Object.getOwnPropertyDescriptor) { |
| iPad | |
| 1024 × 690 In landscape on iOS 4.3 | |
| 1024 × 672 In landscape on iOS 5 | |
| 768 × 946 In portrait on iOS 4.3 | |
| 768 × 928 In portrait on iOS 5 | |
| 1024 × 660 Always showing bookmarks bar in landscape on iOS 4.3 | |
| 1024 × 644 Always showing bookmarks bar in landscape on iOS 5 | |
| 768 × 916 Always showing bookmarks bar in portrait on iOS 4.3 |
| # A simple Makefile alternative to using Grunt for your static asset compilation | |
| # | |
| ## Usage | |
| # | |
| # $ npm install | |
| # | |
| # And then you can run various commands: | |
| # | |
| # $ make # compile files that need compiling | |
| # $ make clean all # remove target files and recompile from scratch |
A complete list of RxJS 5 operators with easy to understand explanations and runnable examples.
