igortik

user  nginx;

# one(1) worker or equal the number of _real_ cpu cores. 4=4 core cpu
worker_processes  4;

# renice workers to reduce priority compared to system processes for
# machine health. worst case nginx will get ~25% system resources at nice=15
worker_priority -5;

VimleshS

Checkout a new working branch

 git checkout -b <branchname>

Make Changes

 git add
 git commit -m "description of changes"

Sync with remote

bcoe

npm Users By Downloads (git.io/npm-top)

---

npm users sorted by the monthly downloads of their modules, for the range May 6, 2018 until Jun 6, 2018.

Metrics are calculated using top-npm-users.

#	User	Downloads

ilyaigpetrov

Meteor Alternatives Per Feature

This table was created in 2015 so may be quite outdated today.

Feature	Meteor Solution	Alternative Solutions	Description
Live DB Sync	[livequery][lq] ([mongo-oplog]), [ddp]	RethinkDB, Redis, ShareDB, [npm:mongo-oplog], [firebase], etc.	Push DB updates to client/server.
Latency Compensation, Optimistic UI	[minimongo][mm]	[RethinkDB][lcr], [mWater/minimongo] (fork, not ws but http, browserify)	Imitate successful db query on client before it is done.
Isomorphic Code	[isobuild] & isopacks	browserify	Write one code for server/client/mobile.
Isomorphic Packaging	[isobuild], atmosphere		No more separate packages for server & client. Get bower + npm + mobile.

jamiewilson

Deploying a Meteor app to Digital Ocean

Table of Contents

1. Create an SSH Key
2. Create a Digital Ocean account and droplet
3. Connect to your server with SSH
4. Create a new user and disable root access
5. Give your new user sudo privileges and add SSH keys to his/her account
6. Disable remote access to root account

aitoroses

export function AnimateMixinFactory(stateName) {

  var animateMixin = {
    getInitialState() {
      return {
        [stateName]: {}
      }
    }
  };

omnibs

Comparative Benchmark Numbers @ Rackspace

I've taken the benchmarks from Matthew Rothenberg's phoenix-showdown, updated Phoenix to 0.13.1 and ran the tests on the most powerful machines available at Rackspace.

Results

Framework	Throughput (req/s)	Latency (ms)	Consistency (σ ms)

ThatRendle

Update, September 2016

OK, you can pretty much ignore what I wrote below this update, because it doesn't really apply anymore.

I wrote this over a year ago, and at the time I had spent a couple of weeks trying to get Kafka 0.8 working with .NET and then Node.js with much frustration and very little success. I was rather angry. It keeps getting linked, though, and just popped up on Hacker News, so here's sort of an update, although I haven't used Kafka at all this year so I don't really have any new information.

In the end, we managed to get things working with a Node.js client, although we continued to have problems, both with our code and with managing a Kafka/Zookeeper cluster generally. What made it worse was that I did not then, and do not now, believe that Kafka was the correct solution for that particular problem at that particular company. What they were trying to achieve could have been done more simply with any number of other messaging systems, with a subscriber reading messages off and writing

tcdevs

• Sprint.js
• Zepto.js
• Snack.js
• $dom
• xui.js
• 140medley
• Minified.js
• Microjs.com
• Sizzlejs.com
• How to create a simple JavaScript library in jQuery style

paulirish

/* bling.js */
window.$ = document.querySelector.bind(document);
window.$$ = document.querySelectorAll.bind(document);
Node.prototype.on = window.on = function(name, fn) { this.addEventListener(name, fn); };
NodeList.prototype.__proto__ = Array.prototype;
NodeList.prototype.on = function(name, fn) { this.forEach((elem) => elem.on(name, fn)); };