Following instructions from the excellent https://www.rinkeby.io/
A full node lets you access all state. There is a light node (state-on-demand) and wallet-only (no state) instructions as well,
<?php | |
namespace f; | |
use ReflectionFunction; | |
const curry = 'f\curry'; | |
function curry(callable $f, ...$args) | |
{ |
Following instructions from the excellent https://www.rinkeby.io/
A full node lets you access all state. There is a light node (state-on-demand) and wallet-only (no state) instructions as well,
As I've been learning more and more about NativeScript, one of the first tasks I really dove into was learning how to customize the Navigation Bar for an iOS app. NativeScript has a Navbar component on the roadmap, but for now, it requires some knowledge about the underlying iOS implementation of UINavigationControllers, UIViewControllers and the like. But fear not! I have braved the treacherous waters of StackOverflow and the Objective-C docs and emerged, victorious and unscathed.
In this article, I’ll go over a few of the more common tweaks that you might be needing to make to the Navigation Bar or Status Bar. While NativeScript is a cross-platform framework, these tweaks apply specifically to iOS. However, most of the items that I will
<!-- MIT License --> | |
<html> | |
<head> | |
<script> | |
function generateKey(alg, scope) { | |
return new Promise(function(resolve) { | |
var genkey = crypto.subtle.generateKey(alg, true, scope) | |
genkey.then(function (pair) { | |
resolve(pair) | |
}) |
<?php | |
interface UrlGeneratorInterface | |
{ | |
/** | |
* Generates a URL for the given route name and parameters. The options | |
* MAY be used to provide hints for the URL generation. This includes | |
* information about different parts of a URL, e.g. the scheme or port to | |
* use or whether absolute or relative URLs should be generated. | |
* |
Native HTML controls are a challenge to style. You can style any element in the web platform that uses Shadow DOM with a pseudo element ::pseudo-element
or the /deep/
path selector.
video::webkit-media-controls-timeline {
background-color: lime;
}
video /deep/ input[type=range] {
Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.
For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.
But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.
SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil
type Monoid<'a> = { | |
unit : 'a | |
op : 'a -> 'a -> 'a | |
} | |
let endo<'a> = | |
{ unit = id | |
op = fun (f:'a -> 'a) (g:'a -> 'a) -> f << g } | |
Use --graph
as option for puppet
in Vagrantfile
:
Vagrant::Config.run do |config|
config.vm.define :devbox do |devbox|
...
devbox.vm.customize ["modifyvm", :id, "--name", "trololo-devbox"]
...
devbox.vm.provision :shell, :inline => "apt-get update --fix-missing"
...
devbox.vm.provision :puppet do |puppet|