Leo Gaskin leotaku

Risk Assessment of GitHub Copilot

0xabad1dea, July 2021

this is a rough draft and may be updated with more examples

GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?

Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to

Synchronized Output

Synchronized output is merely implementing the feature as inspired by iTerm2 synchronized output, except that it's not using the rare DCS but rather the well known SM ? and RM ?. iTerm2 has now also adopted to use the new syntax instead of using DCS.

Semantics

When rendering the screen of the terminal, the Emulator usually iterates through each visible grid cell and renders its current state. With applications updating the screen a at higher frequency this can cause tearing.

This mode attempts to mitigate that.

The list is moving out!

If you share this list, please use this link instead: https://lambdaurora.dev/optifine_alternatives

It may still be only a redirection link, but it will have a better web display of the list soon. And the list being on GitHub/GitHub pages improves load times.

The gist version of this list will stop being updated.

Why?

React

Ant Design - https://ant.design/
Atlaskit by Atlassian - https://atlaskit.atlassian.com/
Base Web by Uber - https://baseweb.design/
Blueprint by Palantir - https://blueprintjs.com/
Carbon by IBM - https://www.carbondesignsystem.com/
Elastic UI by Elastic - https://elastic.github.io/eui/
Evergreen by Segment - https://evergreen.segment.com/

This document contains some ideas for additions to the Nix language.

Motivation

The Nix package manager, Nixpkgs and NixOS currently have several problems:

Poor discoverability of package options. Package functions have function arguments like enableFoo, but there is no way for the Nix UI to discover them, let alone to provide programmatic ways to

Orthodox C++

This article has been updated and is available here.

"Scar Tissues Make Relationships Wear Out"

04/26/2103. From a lecture by Professor John Ousterhout at Stanford, class CS142.

This is my most touchy-feely thought for the weekend. Here’s the basic idea: It’s really hard to build relationships that last for a long time. If you haven’t discovered this, you will discover this sooner or later. And it's hard both for personal relationships and for business relationships. And to me, it's pretty amazing that two people can stay married for 25 years without killing each other.

[Laughter]

> But honestly, most professional relationships don't last anywhere near that long. The best bands always seem to break up after 2 or 3 years. And business partnerships fall apart, and there's all these problems in these relationships that just don't last. So, why is that? Well, in my view, it’s relationships don't fail because there some single catastrophic event to destroy them, although often there is a single catastrophic event around the the end of the relation

	type term =
	\| Lam of (term -> term)
	\| Pi of term * (term -> term)
	\| Appl of term * term
	\| Ann of term * term
	\| FreeVar of int
	\| Star
	\| Box

	let unfurl lvl f = f (FreeVar lvl)

	#![feature(asm)]

	/* For Intel */

	// "Before an application attempts to use AESNI instructions or PCLMULQDQ,
	// the application should follow the steps illustrated in Section 11.6.2,
	// “Checking for SSE/SSE2 Support.” Next, use the additional step provided below:
	// Check that the processor supports AESNI (if CPUID.01H:ECX.AESNI[bit 25] = 1);
	// check that the processor supports PCLMULQDQ (if CPUID.01H:ECX.PCLMULQDQ[bit 1] = 1)."

	# On slow systems, checking the cached .zcompdump file to see if it must be
	# regenerated adds a noticable delay to zsh startup. This little hack restricts
	# it to once a day. It should be pasted into your own completion file.
	#
	# The globbing is a little complicated here:
	# - '#q' is an explicit glob qualifier that makes globbing work within zsh's [[ ]] construct.
	# - 'N' makes the glob pattern evaluate to nothing when it doesn't match (rather than throw a globbing error)
	# - '.' matches "regular files"
	# - 'mh+24' matches files (or directories or whatever) that are older than 24 hours.
	autoload -Uz compinit