All of the following information is based on go version go1.17.1 darwin/amd64
.
GOOS | Out of the Box |
---|---|
aix |
✅ |
android |
✅ |
{ pkgs ? import <nixpkgs> { } }: | |
let | |
demo-program = pkgs.writeShellScriptBin "helloWorld" "while sleep 3; do echo Hello World; done"; | |
demo-service = pkgs.substituteAll { | |
name = "demo.service"; | |
src = ./demo.service.in; | |
demoExe = "${demo-program}/bin/helloWorld"; | |
}; | |
demo-socket = pkgs.concatText "demo.socket" [ ./demo.socket ]; |
#!/usr/bin/awk -f | |
# This program is a copy of guff, a plot device. https://github.com/silentbicycle/guff | |
# My copy here is written in awk instead of C, has no compelling benefit. | |
# Public domain. @thingskatedid | |
# Run as awk -v x=xyz ... or env variables for stuff? | |
# Assumptions: the data is evenly spaced along the x-axis | |
# TODO: moving average |
#!/bin/sh | |
#|-*- mode:lisp -*-|# | |
#| | |
exec ros -Q -- $0 "$@" | |
|# | |
(progn ;;init forms | |
(ros:ensure-asdf) | |
#+quicklisp (ql:quickload '(usocket flexi-streams) :silent t) | |
) |
#!/bin/sh | |
#|-*- mode:lisp -*-|# | |
#| | |
exec ros -Q -- $0 "$@" | |
|# | |
(progn ;;init forms | |
(ros:ensure-asdf) | |
#+quicklisp (ql:quickload '(usocket) :silent t) | |
) |
; Short guide to UDP/IP Client/Server programming in Common Lisp using usockets | |
; | |
; The main reason for this guide is because there are very few examples that | |
; explain how to get started with socket programming with Common Lisp that I | |
; could understand. | |
; After working on a short example on TCP, I found the | |
; need for a UDP tutorial. So, here goes. | |
; As usual, we will use quicklisp to load usocket. |
; Short guide to TCP/IP Client/Server programming in Common Lisp using usockets | |
; | |
; The main reason for this guide is because there are very few examples that | |
; explain how to get started with socket programming with Common Lisp that I | |
; could understand. After spending a day trying, I finally came up with a small | |
; bit of code that makes it easy to understand the basics. I've written this | |
; primarily for myself, but should help others get started as well. | |
; As usual, we will use quicklisp to load usocket. |
##Packaging
##Job Creation
This is just a few thoughts on the topic of writing technical guides. This was intended for Basho's engineering team, but this may apply to open source projects in general.
It's commonly preached that the first step in writing is to identify your audience; to whom are you writing? This is the most well known, most repeated, and most overlooked step of writing in general and technical writing in particular. Take this document, for example. My audience is technical people who need to communicate technical information, and not teenagers, so I shy away from images of pop icons and memes. I use jargon and words like "identify" rather than "peep this".