Gozala

// No need to sub class Array if what you need is just an extended
// array. Example below illustrates the way to extend Array.  

function SubArray() {
  return Object.defineProperties(Array.prototype.slice.call(arguments), SubArrayDescriptor)
}
SubArray.prototype = Array.prototype
var SubArrayDescriptor =
{ constructor: { value: SubArray }
, last: { value: function last() {

ryanflorence

var http = require("http"),
    url = require("url"),
    path = require("path"),
    fs = require("fs")
    port = process.argv[2] || 8888;

http.createServer(function(request, response) {

  var uri = url.parse(request.url).pathname
    , filename = path.join(process.cwd(), uri);

devinrhode2

/**
 * Like, basically PERFECT scrollbars
 */

/* 
   It's pure CSS. 
   Since a quick google search will confirm people going crazy about Mac OS Lion scrollbars...
   this has no fade-out effect.
  
   In Mac OS Lion, the lowest common denominator is always showing scrollbars by a setting.

chad3814

// This is from my comment here: http://wolfram.kriesing.de/blog/index.php/2008/javascript-remove-element-from-array/comment-page-2#comment-466561

/*
 * How to delete items from an Array in JavaScript, an exhaustive guide
 */

// DON'T use the delete operator, it leaves a hole in the array:
var arr = [4, 5, 6];
delete arr[1]; // arr now: [4, undefined, 6]

dustinboston

// Usage: 
//
// 1. Put this in the file that gets first loaded by RequireJS
// 2. Once the page has loaded, type window.rtree.map() in the console
//    This will map all dependencies in the window.rtree.tree object
// 3. To generate UML call window.rtree.toUml(). The output can be used
//    here: http://yuml.me/diagram/scruffy/class/draw
requirejs.onResourceLoad = function (context, map, depMaps) {
  if (!window.rtree) {
    window.rtree = {};

nandosola

import java.lang.reflect.InvocationTargetException;

import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.SwingUtilities;


public class CreateAndShowGUI extends Thread{
	Runnable HelloWorldFrame = new Runnable() {
        public void run() {

mbostock

license: gpl-3.0

creationix

function run(generator) {
  var iterator = generator(resume);
  var data = null, yielded = false;
  
  iterator.next();
  yielded = true;
  check();
  
  function check() {
    while (data && yielded) {

d1manson

  /*  EXAMPLE:
    
  var workerCode = function(){
    "use strict;"  //this will become the first line of the worker
    
    CalculateSomething(a,b,c,d){
        var v = a+b+c+d; //trivial calculation
        main.DisplayResult(v,"hello"); 
    }
  

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions