junosuarez

One could imagine a version of Node built on a hypothetical JavaScript-sans-Arrays. In such a world, packages would have to invent array types for themselves. The lingua franca array would be a number-keyed object, and packages would have to downcast their interpretation of arrays down to number-keyed objects at their thresholds. If a package missed doing this, their definition of an array would leak into calling packages. What if contemporary arrays were introduced into this ecosystem? At some level, they're still just sugar for objects-with-numeric-keys; but they'd have the potential to give packages a global interchange datatype for arrays. At the very least users would start passing them between packages. They'd expect native Arrays to work. Eventually there would be pressure on core to adopt the native Array. Would we do it?

The result of the above hypothetical is not that arrays replace objects, it's that native Arrays replace ad-hoc definitions of arrays. Native Arrays standardize the interchange form

junosuarez

function hi () {
  return 'hi'
}

module.exports = hi

// compiles fine with:
// module.exports = function hi () {
//  return 'hi'
// }

junosuarez

By default monitoring is disabled (threshold set to 0), even if the actual cost of latency
monitoring is near zero. However while the memory requirements of latency monitoring are
very small, there is no good reason to raise the baseline memory usage of a Redis instance
that is working well.

via http://redis.io/topics/latency-monitor

junosuarez

hasOwnProperty check is not necessary.

the advice in Crockford's little javascript book only made sense in a time when it was more common place for people to do really silly things, like add enumerable properties to the global Object object, so it was necessary to be paranoid-level defensive at the expense of code readability. In our codebase, we know that these things aren't happening, so we should prefer readability.

junosuarez

Jason Denizac

API / platform developer based in San Francisco

jason@denizac.org ● Homepage: jden.us

Current

• Full stack engineer at AgileMD

junosuarez

[![quality tested](https://img.shields.io/badge/quality-tested-brightgreen.svg)](https://github.com/jden/quality)

junosuarez

String.prototype.c = function (b) { console.log(this); return this.concat(b) }
String.c(b)

"a".c("b")
VM2531:2 String {0: "a", length: 1, [[PrimitiveValue]]: "a"}
"ab"

("a".c)("b")
VM2531:2 String {0: "a", length: 1, [[PrimitiveValue]]: "a"}
"ab"

junosuarez

#!/usr/bin/env node                                                                            
var path = require('path')                                                                     
var exec = require('child_process').execSync                                                   
                                                                                               
function receive(then) {                                                                       
  process.stdin.on('data', function (data) {                                                   
    then(null, parse(data))                                                                    
  })                                                                                           
}                                                                                              
                                                                                               

junosuarez

<code value="au"/>
 <code value="nz">
   <extension url="http://hl7.org/fhir/Profile/tools-extensions#display">
     <valueString value="New Zealand a.k.a Kiwiland"/>     
   </extension>
 </code>

junosuarez

DO language plpgsql $$ DECLARE result RECORD; BEGIN
select * into result from table limit 1;
RAISE NOTICE '%', result; END$$;