... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
package com.banksimple.util | |
private[util] final class Effectful[T](val origin: T) { | |
/** | |
* A special case of doto, andAlso is useful for | |
* quick logging or output tasks. Similar in use | |
* to doto, but only takes one function. | |
* */ | |
def andAlso(x: T => Unit): T = { x(origin) ; origin } |
#!/usr/bin/bash | |
# Author: Stephen Coley @coleydotco | |
# | |
# This script automates a Github deploy. | |
# I use it with Alfred to deploy http://coley.co. | |
# | |
# Change the stuff surrounded in [..] | |
# | |
# You must run git pull in the terminal and | |
# copy the line that asks you for your password. |
... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
This is a WORK IN PROGRESS intended for fleshing out and feedback
It's very common for people to be unhappy with how a WordPress plugin adds front end resources to their site. If a plugin needs CSS, the plugin will add a <link>
element to that CSS. If the plugin needs JavaScript, it will add a <script>
to that JavaScript.
Plugins do this because it works. It's damn important for a WordPress plugin to work, even in adverse conditions. They rightfully want good ratings and little customer support.
But this comes at the cost of additional HTTP requests. In optimizing front end performance of a site, reducing the number of HTTP requests is a huge thing. Front end developers want to decide and control how front end resources are being handled, and WordPress plugins don't typically make this easy on them.