ukari

This is based on nixpkgs commit 862277ac9d34273cd953f42061e23d488d6b7e8b.

The resulting image is less than 25 MiB compressed.

The actual crosslink closure got shrunk from ~180 MiB to ~60 MiB just by using beam_minimal rather than beam as the base set in beams.nix!

The Freenode resignation FAQ, or: "what the fuck is going on?"

IMPORTANT NOTE:

It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.

Update 3 (May 24, 2021)

A number of things have happened since the last update.

I believe the article was originally written by fede.tft.

It appears they have copied source code to github and updated it for C++11: https://github.com/fedetft/serial-port

Introduction

The serial port protocol is one of the most long lived protocols currently in use. According to wikipedia, it has been standadized in 1969. First, a note: here we're talking about the RS232 serial protocol. This note is necessary because there are many other serial protocols, like SPI, I2C, CAN, and even USB and SATA.

Some time ago, when the Internet connections were done using a 56k modem, the serial port was the most common way of connecting a modem to a computer. Now that we have ADSL modems, the serial ports have disappeared from newer computers, but the protocol is still widely used.

In fact, most microcontrollers, even the newer ones have one or more peripherals capable of communicating using this protocol, and from the PC side, all operating system

JavaScript Static Analysis Tools

Most people are familiar with these three tools:

[JSHint][1]
[JSLint][2]
[Google Closure Linter][3]

The first one is more popular among developers because it is style-agnostic. The other two enforce rules of [Crockford Style][4] and [Google Code Style][5] respectively.

async/await is just the do-notation of the Promise monad

CertSimple just wrote a blog post arguing ES2017's async/await was the best thing to happen with JavaScript. I wholeheartedly agree.

In short, one of the (few?) good things about JavaScript used to be how well it handled asynchronous requests. This was mostly thanks to its Scheme-inherited implementation of functions and closures. That, though, was also one of its worst faults, because it led to the "callback hell", an seemingly unavoidable pattern that made highly asynchronous JS code almost unreadable. Many solutions attempted to solve that, but most failed. Promises almost did it, but failed too. Finally, async/await is here and, combined with Promises, it solves the problem for good. On this post, I'll explain why that is the case and trace a link between promises, async/await, the do-notation and monads.

First, let's illustrate the 3 styles by implementing

	-- Based on: http://augustss.blogspot.com/2007/10/simpler-easier-in-recent-paper-simply.html
	import Data.List (delete, union)
	{- HLINT ignore "Eta reduce" -}

	-- File mnemonics:
	-- env = typing environment
	-- vid = variable identifier in Bind or Var
	-- br = binder variant (Lambda or Pi)
	-- xyzTyp = type of xyz
	-- body = body of Lambda or Pi abstraction

	{-# LANGUAGE GeneralisedNewtypeDeriving #-}

	module Data where

	type UserName = String

	data DataResult = DataResult String
	deriving (Eq, Show)

	class Monad m => Cache m where

	{-# LANGUAGE AllowAmbiguousTypes #-}
	{-# LANGUAGE ConstraintKinds #-}
	{-# LANGUAGE DataKinds #-}
	{-# LANGUAGE FlexibleContexts #-}
	{-# LANGUAGE FlexibleInstances #-}
	{-# LANGUAGE GADTs #-}
	{-# LANGUAGE GeneralizedNewtypeDeriving #-}
	{-# LANGUAGE InstanceSigs #-}
	{-# LANGUAGE KindSignatures #-}
	{-# LANGUAGE PolyKinds #-}

	{-# LANGUAGE
	DeriveFunctor
	, DeriveFoldable
	, DeriveTraversable
	, StandaloneDeriving
	, ViewPatterns
	, PatternSynonyms
	#-}

	-- AST independent

	Shader

	layout (location = 0) in vec3 inPos;
	layout (location = 1) in vec3 inColor;
	layout (location = 2) in vec3 inPosB;
	layout (location = 3) in vec3 inColorB;

	...

	Application