Currently trawling NPM in search of a node module that makes working with CSS and browserified code "feel" better. My first thought was to seek out an existing project (or create one) that took a programmatic approach to CSS generation.
Here's what I've found:
This information source from the following url:
http://peter.sh/experiments/chromium-command-line-switches/
And also in the chromium source:
https://source.chromium.org/chromium/chromium/src/+/main:media/base/media_switches.cc
Slightly disorganized but reasonably complete notes on the algorithms, strategies and optimizations of the Akka Cluster implementation. Could use a lot more links and context etc., but was just written for my own understanding. Might be expanded later.
Links to papers and talks that have inspired the implementation can be found on the 10 last pages of this presentation.
This is the Gossip state representation:
| # How Akka maps to EAI Patterns | |
| Might be up for debate or just plain wrong. Just some notes I scribbled down some time ago. | |
| ----------------------------------------------------------------------------------------------------------------- | |
| EAI PATTERN AKKA PATTERN REFERENCE | |
| ----------------------------------------------------------------------------------------------------------------- | |
| Point to Point Channel Regular Actor Communication http://www.eaipatterns.com/PointToPointChannel.html | |
| Event-Driven Consumer Regular Actor Receive http://www.eaipatterns.com/EventDrivenConsumer.html | |
| Message Selector Actor with Stash http://www.eaipatterns.com/MessageSelector.html |
From: http://run-node.com/littlest-database-that-could/
I've written numerous tiny databases. They don't have much features, but they don't need much features. Usually I'm looking for fast simple key/value stores and Node never disappoints. The point here is, why abstract key value store when JS gives us one for free, as it's most basic component: object.
Will it meet every need? No. But it will meet ALOT of scenarios.
In memory JS object lookups, were talking hundreds of thousands of lookups (you'll easily flood http before the db), and save hundreds of thousands of records in a JSON file written to disk. Not a 200ms r/t to some hosted Redis. Hey, that's fine if that's your thing.
Here's the requirements:
| # based on https://github.com/gnarf/.dotfiles/blob/master/b2g.sh | |
| # ============================================================================= | |
| export FIREFOX="/Applications/FirefoxNightly.app/Contents/MacOS/firefox" | |
| export GAIA_DIR="/Users/millermedeiros/Projects/gaia" | |
| alias firefox="$FIREFOX" | |
| alias b2g-bin="$GAIA_DIR/b2g/Contents/MacOS/b2g-bin" | |
| alias b2g="b2g-bin" |
This is some research focused around looking for node modules that support the development of an application that makes heavy use of a central message bus for cross component communication. The process for identifying potential components was simply to start by looking for packages that depend node the node-redis module, as at this this stage we see redis being the mechanism for powering the bus.
| server { | |
| listen 443; | |
| server_name localhost; | |
| root html; | |
| index index.html index.htm; | |
| ssl on; | |
| ssl_certificate server.crt; | |
| ssl_certificate_key server.key; |
