| ( function( window, undefined ) { | |
| 'use strict'; | |
| // helper function | |
| function capitalize( str ) { | |
| return str.charAt(0).toUpperCase() + str.slice(1); | |
| } | |
| // ========================= getStyleProperty by kangax =============================== |
WARNING: If you're reading this in 2021 or later, you're likely better served by reading:
(This gist was created in 2013 and targeted the legacy GOPATH mode.)
$ ssh -A vm
$ git config --global url."[email protected]:".insteadOf "https://github.com/"
[In reply to https://news.ycombinator.com/item?id=7219005]
Here's the history, hope it helps.
I wrote the original version of the npm registry in a day or two on top of CouchDB. I built it quickly and didn't think much about scale.
Isaacs continued to improve and maintain that code. At one point he even wrote up an open standard for generic js package registries for CommonJS but they didn't seem to care (they were too busy arguing about promises).
At the time I wrote the initial code I was employed at CouchOne and we had a small CouchDB hosting platform operated by Jason Smith which is where we ran the registry free of charge. Later on, after CouchOne was aquired by Membase and became Couchbase, it decided to break off the hosting company and give/sell it to Jason Smith, which became IrisCouch.
I've known people at nodejitsu for years, since before the company even existed. I still consider many of them friends. That said, somebody over there has lost their mind.
Trademarks are an important part of open source. They protect the integrity of the trust that is built by any project. A classic example of why this is the case is Firefox. Suppose that a malware producer takes the Firefox codebase, which is free and open source, packages up their malware with it and then releases it as "Firefox". Then they buy search advertising and suddenly their bad and malicious version of Firefox is the first result on search engines across the web. This is clearly a bad thing for Firefox and open source everywhere, but what can Mozilla do to protect their community of users?
They can't enforce a software license since the use is permitted under the Mozilla Public License. They can, however, enforce on these hypothetical bad actors using their trademark on the word "Fi
| /* | |
| Show a progress element for any form submission via POST. | |
| Prevent the form element from being submitted twice. | |
| */ | |
| (function (win, doc) { | |
| 'use strict'; | |
| if (!doc.querySelectorAll || !win.addEventListener) { | |
| // doesn't cut the mustard. | |
| return; | |
| } |
| // ---- | |
| // libsass (v3.1.0-beta) | |
| // ---- | |
| /// Power function | |
| /// @param {Number} $x | |
| /// @param {Number} $n | |
| /// @return {Number} | |
| @function pow($x, $n) { | |
| $ret: 1; |
| <?php | |
| # Licensed under a CC0 1.0 Universal (CC0 1.0) Public Domain Dedication | |
| # http://creativecommons.org/publicdomain/zero/1.0/ | |
| $mysite = 'https://adactio.com/'; // Change this to your website. | |
| $token_endpoint = 'https://tokens.indieauth.com/token'; | |
| $_HEADERS = array(); | |
| foreach(getallheaders() as $name => $value) { |
Quimby is Walmart's service layer for mobile clients' configuration, CMS, a-b testing setup, and a few other sundry related services. It stitches together a constellation of data sources into a concise menu of API calls that mobile clients make to intialize and configure themselves.
Quimby is a REST service layer based upon the Gogo micro-service framework that we in turn built with Node.js, Hapi, Zookeeper, and Redis. Gogo is able to expose an array of web servers as a single host, and offers the ability to isolate tasks into smaller focused processes, emphasizing scalability and failure recovery. For example, a failure in any micro-service will not affect the life cycle of a request. Gogo also offers the additional features required to build distributed services with shared state, such as leader election.
Anivia is Walmart's mobile analytics platform. It collects user-interaction metrics from mobile devices -- iPhone, iPad, Android, and mWeb. It also processes logging and other metrics from a bunch of mobile services. Anivia allows the business to have real-time insight and reporting into what is going on in the mobile business and provides vital capabilities for developers and ops folks to monitor the health of their services.
Anivia is built on Node.js, Hapi, RabbitMQ, and a multitude of downstream systems including Splunk and Omniture. Anivia is taking in 7,000 events per second on average (as of this writing), which after some fan-out and demuxing comes out to around 20,000 messages per second in flight. These rates are expected to soar leading up to and including Black Friday. The platform has grown in recent months to over 1,000 node processes spanning multiple data centers, gaining features such as link resiliency in the process.
| from pelican import signals | |
| import json, urllib, urlparse, datetime, html5lib, os, codecs | |
| LIVESITEURL = "" | |
| WM_CACHE_PATH = None | |
| WM_CACHE = { | |
| "domains": {}, | |
| "pinged": {} | |
| } |