If you're pulling the same branch from origin (origin/develop -> develop
):
git checkout develop
git fetch origin
git pull --no-commit --log --rebase origin develop
#!/usr/bin/env node | |
console.log('yay gist') |
User A goes to the direct tag of User B and presses the call button. User A is presenting with a calling UI. User B received that call and is shown the being called UI. User B Then presses answer. At this stage both User A and User B are taken into the video chat UI. WebRTC does its thing and the call is initialised.
Downloads
directoryConsolas.ttf
fileInstall font
buttonI have not seen prelease versions utilized pre-1.0.0. It seems fairly pointless since the public API is not finalized yet. They become useful after 1.0.0 is released.
From semver.org:
Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.
Versioned and revised ideas for how to run a good tech company.
Edits can just be plain edited. Redactions must be turned into strikethrough and a comment added stating why the text/point is being removed.
bin/kafka-topics.sh --zookeeper localhost:2181 --list
bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic mytopic
bin/kafka-topics.sh --zookeeper localhost:2181 --alter --topic mytopic --config retention.ms=1000
... wait a minute ...
import React, { Component } from 'react' | |
import Firebase from 'firebase' | |
import ReactFireMixin from 'reactfire' | |
import reactMixin from 'react-mixin' | |
const ref = new Firebase('https://<APPNAME>.firebaseio.com/users') | |
class UsersList extends Component { | |
constructor (props, context) { | |
super(props, context) |
Make writing asynchronous code easier by having a consistent way of propagating "context" across related asynchronous operations. Have the "context" be responsible for async-local-storage, allowing the execution before and after hooks, and "context"-local error handling. Finally make sure that the "context"s are composable.
This feature needs to be part of the platform so that library and framework authors can relay on a common well know API, otherwise adoption will be limited.
rust
by executing this: $ curl -sSf https://static.rust-lang.org/rustup.sh | sh
$ nvm install 4
neon
: $ npm install -g neon-cli
templates/binding.gyp.hbs
of the neon-cli
using a patch from here: https://github.com/dherman/neon-cli/pull/6/commits../<(static_lib)
into <(PRODUCT_DIR)/../../<(static_lib)
$ neon new hello
$ cd hello
Cargo.toml
deps to fetch the latest neon from git: