The argument in favor of Promises for Promises is structured as follows:
- Examples
- Lazy Promises
- Remote Promises
- Partial Results
- Error Handling
- Testing
| # Change Java Runtime: | |
| sudo update-alternatives --config java | |
| # Delete Open-JDK | |
| sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\* | |
| # Change fonts - remove hinting: | |
| http://askubuntu.com/questions/32624/ugly-fonts-in-netbeans-how-can-i-make-it-use-the-system-font | |
| # Change RubyMine AntiAliasing first: |
| package main | |
| import ( | |
| "fmt" | |
| "io" | |
| "os" | |
| "time" | |
| "github.com/dustin/go-humanize" | |
| ) |
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
| Original text here: https://whydavewhy.com/2013/08/16/loyalty-and-layoffs/ |
| #!/usr/bin/env bash | |
| echo ">>> Starting Install Script" | |
| # Update | |
| sudo apt-get update | |
| # Install MySQL without prompt | |
| sudo debconf-set-selections <<< 'mysql-server mysql-server/root_password password root' | |
| sudo debconf-set-selections <<< 'mysql-server mysql-server/root_password_again password root' |
Please behave in a polite, considerate, and inclusive manner in the channel at all times. People volunteer their time in the channel to help people like you with your Laravel problems and some respect (in both directions) will go an extremely long way.
When asking questions in the #laravel channel, please follow these 12 simple rules.
| <html> | |
| <head> | |
| <title>Embedding Elm in HTML!</title> | |
| <script type="text/javascript" src="elm.js"></script> | |
| </head> | |
| <body> | |
| <h1>Stamper</h1> | |
| <div id="stamper" style="width:50%; height:400px;"></div> |
| // initialize the Shanghai component which keeps track of | |
| // shipping data in and out of the Port of Shanghai. | |
| var shanghai = Elm.worker(Elm.Shanghai, { | |
| coordinates:[0,0], | |
| incomingShip: { name:"", capacity:0 }, | |
| outgoingShip: "" | |
| }); | |
| function logger(x) { console.log(x) } | |