| <?php | |
| public function dump(DirectedAdjacencyList $func, $filename) { | |
| $ctr = 0; | |
| $graph = Graph::create("dump"); | |
| $nodes = new \SplObjectStorage; | |
| $scope = new \SplObjectStorage; | |
| foreach ($func->eachVertex() as $vertex => $_) { | |
| $nodes[$vertex] = Node::create('node_' . $ctr++); | |
| $graph->setNode($nodes[$vertex]); |
| (require '[clojure.core.async :as a]) | |
| (def xform (comp (map inc) | |
| (filter even?) | |
| (dedupe) | |
| (flatmap range) | |
| (partition-all 3) | |
| (partition-by #(< (apply + %) 7)) | |
| (flatmap flatten) | |
| (random-sample 1.0) |
This is a guide on how to email securely.
There are many guides on how to install and use PGP to encrypt email. This is not one of them. This is a guide on secure communication using email with PGP encryption. If you are not familiar with PGP, please read another guide first. If you are comfortable using PGP to encrypt and decrypt emails, this guide will raise your security to the next level.
| Turning The Design Clock Back | |
| Object-oriented design principles haven't had the effect we hoped for. The | |
| SOLID principles are excellent design guidelines, but experience shows that | |
| programmers find them difficult to follow. What do we do about this? | |
| Surprisingly, the Structured Design literature of forty years ago contains | |
| compelling solutions to many current design problems. They're simple and easy | |
| to understand, but were lost in the noise as OO rose to popularity. We'll | |
| reinterpret these simple design ideas in a modern context, finding that many of | |
| our most promising new design ideas resemble them. Rapid web application |
Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.
For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.
But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.
SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil
... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
| package main | |
| import ( | |
| "fmt" | |
| "github.com/sdboyer/transducers-go" | |
| ) | |
| func FizzyBuzzyNumbers() transducers.ValueStream { | |
| fizzyBuzzyCurr := 0 |
| // Have some complicated non-React widgets that manipulate DOM? | |
| // Do they manage a list of DOM elements? Here's how to wrap it | |
| // into a React component so you can "constantly rerender" it. | |
| // A dumb non-react widget that manually manage some DOM node that | |
| // represent a list of items | |
| function NonReactWidget(node) { | |
| this.node = node; | |
| } |
| const I = x => x | |
| const K = x => y => x | |
| const A = f => x => f (x) | |
| const T = x => f => f (x) | |
| const W = f => x => f (x) (x) | |
| const C = f => y => x => f (x) (y) | |
| const B = f => g => x => f (g (x)) | |
| const S = f => g => x => f (x) (g (x)) | |
| const S_ = f => g => x => f (g (x)) (x) | |
| const S2 = f => g => h => x => f (g (x)) (h (x)) |
