Hasan Bayat hasanbayatme

Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)

Code Example

Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.

Motivation

Problem: When linking to the raw version of a gist, the link changes with each revision.

Solution:

To return the first file from a gist: https://gist.github.com/[gist_user]/[gist_id]/raw/

Example: https://gist.github.com/atenni/5604522/raw/
Works even when you change the filename.

To get a file from multi–file gist: https://gist.github.com/[gist_user]/[gist_id]/raw/[file_name]

building your first node module

This is pretty simple, lets dive in!

choose a name

Find a name that isn't taken and clearly describes what your module is doing

$ npm view your-first-node-module

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

	public static class ObjectToDictionaryHelper
	{
	public static IDictionary<string, object> ToDictionary(this object source)
	{
	return source.ToDictionary<object>();
	}

	public static IDictionary<string, T> ToDictionary<T>(this object source)
	{
	if (source == null)

	// Credit to damien_oconnell from http://forum.unity3d.com/threads/39513-Click-drag-camera-movement
	// for using the mouse displacement for calculating the amount of camera movement and panning code.

	using UnityEngine;
	using System.Collections;

	public class MoveCamera : MonoBehaviour
	{
	//
	// VARIABLES

	# sleepy flower girl
	(◡ ‿ ◡ ✿)

	# y u no
	ლ(ಠ益ಠლ)

	# smiling breasts
	（^人^）

	# flipping tables

	/*
	* Created by C.J. Kimberlin (http://cjkimberlin.com)
	*
	* The MIT License (MIT)
	*
	* Copyright (c) 2014
	*
	* Permission is hereby granted, free of charge, to any person obtaining a copy
	* of this software and associated documentation files (the "Software"), to deal
	* in the Software without restriction, including without limitation the rights

	/***
	* This script will anchor a GameObject to a relative screen position.
	* This script is intended to be used with ViewportHandler.cs by Marcel Căşvan, available here: http://gamedev.stackexchange.com/a/89973/50623
	* It is also copied in this gist below.
	*
	* Note: For performance reasons it's currently assumed that the game resolution will not change after the game starts.
	* You could not make this assumption by periodically calling UpdateAnchor() in the Update() function or a coroutine, but is left as an exercise to the reader.
	*/
	/* The MIT License (MIT)

	using Microsoft.CSharp;
	using System.CodeDom;
	using System.CodeDom.Compiler;
	using System.Collections.Generic;
	using System.Collections.ObjectModel;
	using System.Collections.Specialized;
	using System.IO;
	using System.Linq;
	using System.Reflection;
	using System.Text;