| var QUEUE_URL = 'https://sqs.us-east-1.amazonaws.com/{AWS_ACCUOUNT_}/matsuoy-lambda'; | |
| var AWS = require('aws-sdk'); | |
| var sqs = new AWS.SQS({region : 'us-east-1'}); | |
| exports.handler = function(event, context) { | |
| var params = { | |
| MessageBody: JSON.stringify(event), | |
| QueueUrl: QUEUE_URL | |
| }; | |
| sqs.sendMessage(params, function(err,data){ |
| #printf | |
| RUN printf '#!/bin/bash\n\ | |
| echo hello world from line 1\n\ | |
| echo hello world from line 2'\ | |
| >> /tmp/hello | |
| #echo | |
| RUN echo -e '#!/bin/bash\n\ | |
| echo hello world from line 1\n\ | |
| echo hello world from line 2'\ |
| Latency Comparison Numbers | |
| -------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
| 'use strict'; | |
| function rxDecorateDirective($provide, directiveName) { | |
| // Duck-typing function lifted from the rx.js source. | |
| function isObservable(obj) { | |
| return obj && typeof obj.subscribe === 'function'; | |
| } | |
| $provide.decorator(directiveName + 'Directive', ['$delegate', 'rx', function($delegate, rx) { | |
| var directiveConfig = $delegate[0]; |
There's been a strange explosion in misinformation about browserify recently, particularly in comparisons to webpack.
Generally speaking, most of this confusion stems from how webpack is more willing to pull features into its core to ease discoverability while browserify is more likely to push features out to userland instead.
I think that longer-term, separability has more benefits from a maintenance and
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <script src="https://cdn.rawgit.com/lodash/lodash/3.0.1/lodash.min.js"></script> | |
| <meta name="description" content="Exercise Blank"> | |
| <meta charset="utf-8"> | |
| <title>JS Bin</title> | |
| </head> | |
| <body> |
(by @andrestaltz)
So you're curious in learning this new thing called Reactive Programming, particularly its variant comprising of Rx, Bacon.js, RAC, and others.
Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:
Rx.Observable.prototype.flatMapLatest(selector, [thisArg])
Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.
