Socheat Sok socheatsok78

Golang - Building Executables for Different Architectures

env GOOS=target-OS GOARCH=target-architecture go build package-import-path

# Example
env GOOS=darwin GOARCH=amd64 go build
env GOOS=darwin GOARCH=amd64 go build main.go
env GOOS=darwin GOARCH=amd64 go build github.com/zoo/york/foo/bar

README

Create a template service file at /etc/systemd/system/[email protected]. The template parameter will correspond to the name of target host:

[Unit]
Description=Setup a secure tunnel to %I
After=network.target

Default behavior dictates the following order for ZSH startup files:

/etc/zshenv
~/.zshenv
/etc/zprofile (if login shell)
~/.zprofile (if login shell)
/etc/zshrc (if interactive)
~/.zshrc (if interactive)
/etc/zlogin (if login shell)
~/.zlogin (if login shell)

INTRO

Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".

Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).

Let's dig in:

Goroutines

Google Public NTP [AS15169]:

time.google.com

time1.google.com

time2.google.com

time3.google.com

Moved to git-repository: https://github.com/denji/awesome-http-benchmark

Tools

Located in alphabetical order (not prefer)

ab – slow and single threaded, written in C
apib – most of the features of ApacheBench (ab), also designed as a more modern replacement, written in C
autocannon – fast HTTP/1.1 benchmarking tool written in Node.js
baloo – Expressive end-to-end HTTP API testing made easy, written in Go (golang)

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

	package main

	import (
	"context"
	"flag"
	"fmt"
	"io"
	"net"
	"net/http"
	"os"

	# Detect operating system in Makefile.
	# Author: He Tao
	# Date: 2015-05-30

	OSFLAG :=
	ifeq ($(OS),Windows_NT)
	OSFLAG += -D WIN32
	ifeq ($(PROCESSOR_ARCHITECTURE),AMD64)
	OSFLAG += -D AMD64
	endif

	import javax.net.ssl.SSLParameters;
	import javax.net.ssl.SSLSocket;
	import javax.net.ssl.SSLSocketFactory;
	import java.io.BufferedReader;
	import java.io.BufferedWriter;
	import java.io.IOException;
	import java.io.InputStreamReader;
	import java.io.OutputStreamWriter;
	import java.net.Socket;