mattmcmanus

// MIXINS

vendor(prop, args)
  -webkit-{prop} args
  -moz-{prop} args
  -o-{prop} args
  {prop} args

animation()
  vendor('animation', arguments)

navinpai

Simple blinking cursor... code from http://xip.io/ ... Ofcourse I don't own the code! Just keeping it here as a reference of the CSS3 code used.

nikcub

In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:

http://techcrunch.com/2007/08/11/facebook-source-code-leaked/

It became a big deal:

http://www.techmeme.com/070812/p1#a070812p1

The two files are index.php (the homepage) and search.php (the search page)

olistik

# place this file in ~/.config/terminator/config
[global_config]
  title_transmit_bg_color = "#d30102"
  focus = system
[keybindings]
  reset_clear = <Ctrl>R
  new_tab = <Ctrl>T
  split_horiz = <Ctrl><Shift>E
  split_vert = <Ctrl>E
  close_term = <Ctrl><Shift>W

danro

#!/bin/sh
 
if [ $(ps aux | grep $USER | grep node | grep -v grep | wc -l | tr -s "\n") -eq 0 ]
then
  export PATH=/usr/local/bin:$PATH
  export NODE_ENV=production
  cd /path/to/app && forever --spinSleepTime 10000 start server.js >> forever.log 2>&1
fi

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

machty

Query Param API Examples

• Search queries
• Sort: client-side, no refiring of model hook
• Sort: server-side, refire model hook
• Pagination + Sorting
• Boolean values. False value removes QP from URL
• Global query params on app route
• Opt-in to full transition via refresh()
• replaceUrl by changing controller QP property

m19

(function() {
    /*global Ember*/
    /*global DS*/
    /*global io*/
    /*global _*/
    'use strict';

    var RSVP = Ember.RSVP;
    var get = Ember.get;

tonymtz

# first:
lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom | while read f; do  sudo rm /usr/local/${f}; done
sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.*

# To recap, the best way (I've found) to completely uninstall node + npm is to do the following:

# go to /usr/local/lib and delete any node and node_modules
cd /usr/local/lib
sudo rm -rf node*

samselikoff

This post is also on my blog, since Gist doesn't support @ notifications.

---

Components are taking center stage in Ember 2.0. Here are some things you can do today to make the transition as smooth as possible:

• Use Ember CLI
• In general, replace views + controllers with components
• Only use controllers at the top-level for receiving data from the route, and use Ember.Controller instead of Ember.ArrayController or Ember.ObjectController
• Fetch data in your route, and set it as normal properties on your top-level controller. Export an Ember.Controller, otherwise a proxy will be generated. You can use Ember.RSVP.hash to simulate setting normal props on your controller.