Yet another framework syndrome
Name | Date | URL | Stars |
---|---|---|---|
Jake | April 2010 | https://github.com/mde/jake | 848 |
Grunt | March 2012 | http://gruntjs.com/ | 7459 |
Yet another framework syndrome
Name | Date | URL | Stars |
---|---|---|---|
Jake | April 2010 | https://github.com/mde/jake | 848 |
Grunt | March 2012 | http://gruntjs.com/ | 7459 |
» brew install graphicsmagick -v | |
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 | |
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 | |
==> Downloading https://downloads.sourceforge.net/project/graphicsmagick/graphicsmagick/1.3.19/GraphicsMagick-1.3.19.tar.bz2 | |
Already downloaded: /Library/Caches/Homebrew/graphicsmagick-1.3.19.tar.bz2 | |
==> Verifying graphicsmagick-1.3.19.tar.bz2 checksum | |
tar xf /Library/Caches/Homebrew/graphicsmagick-1.3.19.tar.bz2 | |
==> ./configure --prefix=/usr/local/Cellar/graphicsmagick/1.3.19_1 --disable-dependency-tracking --enable-shared --disable-static --with-modules --disable-openmp --without-gslib --with-gs-font-dir=/usr/local/share/ghostscript/fonts --without-x --without-lcms --without-lcms2 | |
configuring GraphicsMagick 1.3.19 | |
checking build system type... x86_64-apple-darwin13.1.0 |
I hereby claim:
To claim this, I am signing this object:
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.
var rinvalid = /[^\x20\x2D0-9A-Z\x5Fa-z\xC0-\xD6\xD8-\xF6\xF8-\xFF]/g; | |
var raccents = /[\xC0-\xFF]/g; | |
var accents = [ | |
[/[\xC0-\xC5]/g, 'A'], | |
[/[\xC6]/g, 'AE'], | |
[/[\xC7]/g, 'C'], | |
[/[\xC8-\xCB]/g, 'E'], | |
[/[\xCC-\xCF]/g, 'I'], | |
[/[\xD0]/g, 'D'], | |
[/[\xD1]/g, 'N'], |
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 |
Hey there!
I'm pleased to announce that [the Pony Foo blog][1] has been completely rewritten from scratch! I've put a few months into it, but I got in many improvements, which I'm going to write a few articles about. Firstly, I wanted to write this email to introduce you to some of the concepts introduced to the engine.
The blog is now backed by [NGINX][3], properly and aggressively caching static assets. I'm using [recluster][4] to achieve zero-downtime deployments while keeping the application servers on two separate processes. I've moved away from Heroku, and now the production environment is hosted on AWS EC2. It's provisioned, configured with sensitive environment variables, and deployed-to using [fast bash scripts][5].
Bash? Non-sense!
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
b