bevacqua

List of JavaScript Build Tools

Yet another framework syndrome

Name	Date	URL	Stars
Jake	April 2010	https://github.com/mde/jake	848
smoosh	March 2011	https://github.com/fat/smoosh	316
anvil.js	February 2012	http://anviljs.com/	160
Grunt	March 2012	http://gruntjs.com/	7459

bevacqua

Sublime Text 2 - Useful Shortcuts

Tested in Mac OS X: super == command

Open/Goto

---

• super+t: go to file
• super+ctrl+p: go to project
• super+r: go to methods

bevacqua

JSConf Slides, Codes and Notes

These are all the JSConf 2014 slides, codes, and notes I was able to cull together from twitter. Thanks to the speakers who posted them and thanks to @chantastic for posting his wonderful notes.

Modular frontend with NPM - Jake Verbaten (@Raynos)

• tweet
• slides and code

bevacqua

IMPORTANT! Remember to check out the wiki page at https://github.com/bebraw/jswiki/wiki/Game-Engines for the most up to date version. There's also a "notes" column in the table but it simply does not fit there... Check out the raw version to see it.

This table contains primarily HTML5 based game engines and frameworks. You might also want to check out the [[Feature Matrix|Game-Engine-Feature-Matrix]], [[Game Resources]] and [[Scene Graphs]].

Name	Size (KB)	License	Type	Unit Tests	Docs	Repository	Notes
Akihabara	453	GPL2, MIT	Classic Repro	no	API	github	Intended for making classic arcade-style games in JS+HTML5
AllBinary Platform	Platform Dependent	AllBinary	2D/2.5D/3D	n

bevacqua

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

bevacqua

function beep(){
  process.stdout.write("\u0007");
}

bevacqua

# Ensures all line endings are committed as LF, but will checkout with native line endings
* text=auto

# -- Override Section, just in-case Git tries to be sneaky

# Ensure that these files are recognized as text
*.asp       text
*.aspx      text
*.asx       text
*.css       text

bevacqua

 http {
    proxy_cache_path  /var/cache/nginx levels=1:2 keys_zone=one:8m max_size=3000m inactive=600m;
    proxy_temp_path /var/tmp;
    include       mime.types;
    default_type  application/octet-stream;
    sendfile        on;
    keepalive_timeout  65;

    gzip on;
    gzip_comp_level 6;

bevacqua

server {
    listen 80;
    server_name konklone.com;
    return 301 https://$host$request_uri;
}

# optional: the 'spdy' at the end of the listen command below turns on SPDY support.

server {
    listen 443 ssl spdy;

bevacqua

echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://npmjs.org/install.sh | sh