// "creature" by dave :) | |
int[][] result; | |
float t, c; | |
float ease(float p) { | |
return 3*p*p - 2*p*p*p; | |
} | |
float ease(float p, float g) { |
This is a play proposal for a new wrapper around go build
that would build your binary but
wrap it in code that would prepare isolation around your binary on run.
A concept of this is in https://github.com/jfrazelle/binctr, in that it takes a docker image and embeds the contents into a final binary so you have a self-contained binary.
The binctr example is unnessesarily heavy for go
binaries because all you need is a completely static
binary.
{ | |
"AWSTemplateFormatVersion" : "2010-09-09", | |
"Parameters" : { | |
"KeyName": { | |
"Type": "AWS::EC2::KeyPair::KeyName", | |
"Description": "Name of an existing EC2 KeyPair to enable SSH access to the ECS instances" | |
}, | |
"SubnetID": { | |
"Type": "List<AWS::EC2::Subnet::Id>", | |
"Description": "List of an existing subnet IDs to use for the load balancer and auto scaling group" |
[EN] The following are the requirements especified for every workshop, make sure to have installed in your computer the software listed for the workshop you are going to attend before it's beginning.
[ES] Los siguientes son los requerimientos especificados para cada workshop, asegúrate de instalar en tu computador el software listado para el workshop que vas a asistir antes de su inicio.
### Videojuegos con JavaScript & Box2D | Fredy Mena ---
/* | |
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 | |
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
copies of the Software, and to permit persons to whom the Software is |
A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."
- Does the design expect failures to happen regularly and handle them gracefully?
- Have we kept things as simple as possible?