A quick overview of the node.js streams interface with basic examples.
This is based on @brycebaril's presentation, Node.js Streams2 Demystified
Streams are a first-class construct in Node.js for handling data.
Think of them as as lazy evaluation applied to data.
| (* | |
| Interactive approach | |
| -------------------- | |
| You can copy-paste code into `utop`, provided you load the lwt.unix | |
| package: | |
| #use "topfind";; | |
| #require "lwt.unix";; |
| //------------------------------------------------------------- | |
| // | |
| // Hypothesis: | |
| // | |
| // Promises/A is a Monad | |
| // | |
| // To be a Monad, it must provide at least: | |
| // - A unit (aka return or mreturn) operation that creates a corresponding | |
| // monadic value from a non-monadic value. | |
| // - A bind operation that applies a function to a monadic value |
| # Install ARCH Linux with encrypted file-system and UEFI | |
| # The official installation guide (https://wiki.archlinux.org/index.php/Installation_Guide) contains a more verbose description. | |
| # Download the archiso image from https://www.archlinux.org/ | |
| # Copy to a usb-drive | |
| dd if=archlinux.img of=/dev/sdX bs=16M && sync # on linux | |
| # Boot from the usb. If the usb fails to boot, make sure that secure boot is disabled in the BIOS configuration. | |
| # Set swedish keymap |
| input { | |
| lumberjack { | |
| # The port to listen on | |
| port => 5043 | |
| # The paths to your ssl cert and key | |
| ssl_certificate => "/etc/pki/tls/certs/logstash-forwarder/logstash-forwarder.crt" | |
| ssl_key => "/etc/pki/tls/private/logstash-forwarder/logstash-forwarder.key" | |
| # default type, but this will already be set by logstash-forwarder anyways |
| obj-m += tcp_svr_sample.o | |
| all: | |
| make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules | |
| clean: | |
| make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clea |
| package main | |
| import ( | |
| "fmt" | |
| "io" | |
| "io/ioutil" | |
| "net" | |
| "os" | |
| "strings" |
| Driver: | |
| -Write the code according to the navigator's specification | |
| -Listen intently to the navigators instructions | |
| -Ask questions wherever there is a lack of clarity | |
| -Offer alternative solutions if you disagree with the navigator | |
| -Where there is disagreement, defer to the navigator. If their idea fails, get to failure quickly and move on | |
| -Make sure code is clean | |
| -Own the computer / keyboard | |
| -Ignore larger issues and focus on the task at hand | |
| -Trust the navigator - ultimately the navigator has the final say in what is written |
