The allocator may yield to the OS when requesting or releasing memory (e.g. sbrk, mmap, munmap)?
232 karma · joined November 19, 2010
The allocator may yield to the OS when requesting or releasing memory (e.g. sbrk, mmap, munmap)?
Sherlock is changing the way SaaS businesses understand and operationalize their product engagement data. Built by a team of SaaS veterans, we are the only product engagement scoring application on the market today. We have found success with our early customers and are ready to expand the team to accelerate our growth. We offer a competitive salary and benefits and are excited to build out the team further.
Email chris@^ or apply here: https://angel.co/sherlock-4/jobs/488709-full-stack-engineer
There are also some bindings for Go: https://github.com/chriso/go-intern
requests = 0
for key in gauged.keys('requests:'):
requests += gauged.aggregate(key, Gauged.SUM, start=-Gauged.WEEK)Full-stack developer from Sydney, Australia. I'm a Javascript (Node.js), Python and C expert.
cohara87 (at) gmail.com
Still active, although development has slowed down.
If you have any questions or issues just submit an issue @ Github and I'll help asap.
Generators are provided by V8, don't require an external fibers extension (i.e. hack), and will be available in the next node stable via `node --harmony-generators`.
Here's an example for those interested: https://github.com/visionmedia/co
switch (count($args)) {
case 0: $method(); break;
case 1: $method($args[0]); break;
case 2: $method($args[0], $args[1]); break;
//etc
default: call_user_func_array($method, $args); break;
}My point is that you can't just de-obfuscate a primarily client-side JS app and replace the Firebase (or whatever) endpoints. Proprietary obfuscation is more than just variable name munging and minification..
It exposes useful constructs such as a social graph, bloom filter, full-text index, and a very fast rate limiter (http://chris6f.com/rate-limiting-with-redis).