Wayne Ashley Berry wayneashleyberry

Awesome PHP

Awesome PHP has been relocated permanently to its own Github repository. No further updates will made to this gist.

Please open an issue for any new suggestions.

(tl;dr DOM builders like [domo][domo] trump HTML templates on the client.)

Like all web developers, I've used a lot of template engines. Like most, I've also written a few of them, some of which even [fit in a tweet][140].

The first open-source code I ever wrote was also one of the the first template engines for node.js, [a port][node-tmpl] of the mother of all JavaScript template engines, [John Resig][jresig]'s [micro-templates][tmpl]. Of course, these days you can't swing a dead cat without hitting a template engine; one in eight packages on npm ([2,220][npm templates] of 16,226 as of 10/19) involve templates.

John's implementation has since evolved and [lives on in Underscore.js][underscore], which means it's the default choice for templating in Backbone.js. And for a while, it's all I would ever use when building a client-side app.

But I can't really see the value in client-side HTML templates anymore.

Never Expose DB Results Directly

If you rename a field, then your users are fucked. Convert with a hardcoded array structure.
Most DB drivers [for PHP] will show integers as numeric strings and false as "0", so you want to typecast them.
Unless you're using an ORM with "hidden" functionality, people will see passwords, salts and all sorts of fancy codes. If you add one and forget to put it in your $hidden array then OOPS!

Use the URI sparingly, and correctly

Use the query string for paired params instead of /users/id/5/active/true. Your API does not need to be SEO optimised.
?format=xml is stupid, use an Accept: application/xml header. I added this to the CodeIgniter Rest Server once for lazy people, and now people think it's a thing. It's not.

Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward discussions repo

io.js - what you need to know

io is a fork of node v0.12 (the next stable version of node.js, currently unreleased)
io.js will be totally compatible with node.js
the people who created io.js are node core contributors who have different ideas on how to run the project
it is not a zero-sum game. many core contributors will help maintain both node.js and io.js

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

from streams session

end-of-stream - specify a callback to be called when a stream ends (which is surpsingly hard to get right)
duplexify - compose a Duplex stream from a Readable and a Writable stream
pump - pipe streams together and close all of them if one of them closes
pumpify - combine an array of streams into a single duplex stream using pump and duplexify
through2 - tools for making Transform streams
from2 - tools for making Readable streams

from "participatory modules" session

	#301 Redirects for .htaccess

	#Redirect a single page:
	Redirect 301 /pagename.php http://www.domain.com/pagename.html

	#Redirect an entire site:
	Redirect 301 / http://www.domain.com/

	#Redirect an entire site to a sub folder
	Redirect 301 / http://www.domain.com/subfolder/

	/**
	* simple mustache-like templater
	* http://mir.aculo.us/2011/03/09/little-helpers-a-tweet-sized-javascript-templating-engine/
	* -----------------------------------------------------------------------------------------
	* t('Hello, {{planet}}!', array('planet' => 'World');
	* returns 'Hello, World!';
	*/
	function t(s,d){
	for(var p in d)
	s=s.replace(new RegExp('{{'+p+'}}','g'), d[p]);

	<!-- standard viewport tag to set the viewport to the device's width
	, Android 2.3 devices need this so 100% width works properly and
	doesn't allow children to blow up the viewport width-->
	<meta name="viewport" id="vp" content="initial-scale=1.0,user-scalable=no,maximum-scale=1,width=device-width" />
	<!-- width=device-width causes the iPhone 5 to letterbox the app, so
	we want to exclude it for iPhone 5 to allow full screen apps -->
	<meta name="viewport" id="vp" content="initial-scale=1.0,user-scalable=no,maximum-scale=1" media="(device-height: 568px)" />
	<!-- provide the splash screens for iPhone 5 and previous -->
	<link href="assets/splashs/splash_1096.png" rel="apple-touch-startup-image" media="(device-height: 568px)">
	<link href="assets/splashs/splash_iphone_2x.png" rel="apple-touch-startup-image" sizes="640x960" media="(device-height: 480px)">

	'use strict';

	var React = require('react');
	React.Component.extend = require('extendible');

	var MyComponent = React.Component.extend({
	state: {
	what: 'extend'
	},
	render: function () {