Richard Willis badsyntax

# Install AVD files
yes | $ANDROID_HOME/tools/bin/sdkmanager --install 'system-images;android-29;default;x86'
yes | $ANDROID_HOME/tools/bin/sdkmanager --licenses

# Create emulator
echo "no" | $ANDROID_HOME/tools/bin/avdmanager create avd -n Pixel_API_29_AOSP -d pixel --package 'system-images;android-29;default;x86' --force

$ANDROID_HOME/emulator/emulator -list-avds

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.

Learn Go in ~5mins

This is inspired by A half-hour to learn Rust and Zig in 30 minutes.

Basics

Your first Go program as a classical "Hello World" is pretty simple:

First we create a workspace for our project:

Installation

apt-get install snapd
snap install microk8s --classic --channel=1.18/stable
microk8s enable dns dashboard registry helm3 ingress storage

Dashboard

Questions:

Can we avoid installing Discourse as root? Cf. https://meta.discourse.org/t/install-issues-when-not-root/16538/17

How to install Discourse 2.4+ on Dokku (2019)

Discourse is very clear that they do not support anything else than their official install instructions, which more or less requires a dedicated server.

Install and Create Emulators using AVDMANAGER and SDKMANAGER

TL;DR

For an emulator that mimics a Pixel 5 Device with Google APIs and ARM architecture (for an M1/M2 Macbook):

List All System Images Available for Download: sdkmanager --list | grep system-images
Download Image: sdkmanager --install "system-images;android-30;google_atd;arm64-v8a"

The Problem

ASP.NET core has a very useful dev-certs utility capable of producing self-signed certificates for local https development work.

This works for the most-part, but as soon as you start wanting to do local development of a native app, iOS refuses to trust the certificate, or indeed, to even let you tell it to trust it.

You can see This Issue for some more context.

The Solution

This is what worked for me, I make no guarantees as to its efficiency or ongoing efficacy.

The Rules of React

All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.

What Functions Are "Pure"?

A number of methods in React are assumed to be "pure".

On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.

	#!/usr/bin/bash

	declare -a repos=(
	"$HOME/Projects/myproject/testing/.git"
	"$HOME/Projects/myproject/testing-bundle/.git"
	"$HOME/Projects/myproject/service-skeleton/.git"
	"$HOME/Projects/myproject/documentation-web/.git"
	"$HOME/Projects/myproject/documentation-api/.git"
	"$HOME/Projects/myproject/coding-standard/.git"
	"$HOME/Projects/myproject/context/microservice1/.git"

	import org.gradle.api.logging.LogLevel;
	import org.gradle.api.logging.Logging;
	import org.slf4j.Marker;

	/**
	* Created by ahasbini on 11-Oct-19.
	*/
	public class Logger implements org.gradle.api.logging.Logger {

	private static boolean useQuietLogs = false;