ibc

/Google\ Chrome\ Canary --enable-logging --v=1  --vmodule=*/webrtc/*=2,*/libjingle/*=2,*=-2 --enable-logging=stderr

// Easier:

/Google\ Chrome\ Canary --enable-logging --v=1  --vmodule=*/webrtc/*=2,*=-2 --enable-logging=stderr

walm

package main

import (
	"fmt"
	"log"
	"strconv"

	"github.com/miekg/dns"
)

rms1000watt

package main

import (
	"fmt"
	"os"
	"text/template"
)

type Person struct {
	Name string

oncode

Reference for How to Write an Open Source JavaScript Library

The purpose of this document is to serve as a reference for:

How to Write an Open Source JavaScript Library course by Kent C. Dodds

Watch the series at egghead.io, if you haven't.

---

Sean-Der

FROM debian:sid
ENV DISPLAY :0

RUN echo 'deb http://mirrors.kernel.org/debian/ sid main contrib non-free\n\
deb-src http://mirrors.kernel.org/debian/ sid main contrib non-free\n'\
>> /etc/apt/sources.list

RUN apt-get -y update
RUN apt-get -y install git build-essential bison flex cmake
RUN apt-get -y build-dep gstreamer1.0-libav gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly

XueshiQiao

AnnexB format:

([start code] NALU) | ( [start code] NALU) |

AVCC format:

([extradata]) | ([length] NALU) | ([length] NALU) |

StevenACoffman

From You're not actually building microservices

So, are you building microservices? Take a look at a few of these symptoms, and decide for yourself:

• ❌ A change to one microservice often requires changes to other microservices
• ✅ Deploying one microservice requires other microservices to be deployed at the same time
• ❓ Your microservices are overly chatty
• ❌ The same developers work across a large number of microservices
• ✅ Many of your microservices share a datastore
• ✅ Your microservices share a lot of the same code or models