Rom Grk romgrk

🗺🐘 1000+ PostgreSQL EXTENSIONs

This is a list of URLs to PostgreSQL EXTENSION repos, listed in alphabetical order of parent repo, with active forks listed under each parent.

⭐️ >= 10 stars
⭐️⭐️ >= 100 stars
⭐️⭐️⭐️ >= 1000 stars
Numbers of stars might not be up-to-date.

REST considered harmful

Albeit the title might (probably) be a bit inflammatory, I've come to feel like REST is a bad solution for the problem that it solves.

The thing with REST, is that at its core, it's basically a RPC (Remote Procedure Call) that we've been trying to cram in the HTTP protocol. There is no good reason to do that. HTTP wasn't made for this, and we should instead be abstracting that layer away instead of trying to use it for purposes it isn't meant to fulfill.

A half-hour to learn Zig

This is inspired by https://fasterthanli.me/blog/2020/a-half-hour-to-learn-rust/

Basics

the command zig run my_code.zig will compile and immediately run your Zig program. Each of these cells contains a zig program that you can try to run (some of them contain compile-time errors that you can comment out to play with)

Profiling performance

Using perf:

$ perf record -g binary
$ perf script | stackcollapse-perf.pl | rust-unmangle | flamegraph.pl > flame.svg

NOTE: See @GabrielMajeri's comments below about the -g option.

Edit — February 2019

This gist had a far larger impact than I imagined it would, and apparently people are still finding it, so a quick update:

TC39 is currently moving forward with a slightly different version of TLA, referred to as 'variant B', in which a module with TLA doesn't block sibling execution. This vastly reduces the danger of parallelizable work happening in serial and thereby delaying startup, which was the concern that motivated me to write this gist
In the wild, we're seeing (async main(){...}()) as a substitute for TLA. This completely eliminates the blocking problem (yay!) but it's less powerful, and harder to statically analyse (boo). In other words the lack of TLA is causing real problems
Therefore, a version of TLA that solves the original issue is a valuable addition to the language, and I'm in full support of the current proposal, which you can read here.

I'll leave the rest of this document unedited, for archaeological

Setup redis-cli on AWS EC2

SSH into your EC2 instance. Run the following:

$ sudo yum install gcc This may return an "already installed" message. That's OK.

$ wget http://download.redis.io/redis-stable.tar.gz && tar xvzf redis-stable.tar.gz && cd redis-stable && make

See: http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/GettingStarted.ConnectToCacheNode.Redis.html

	/*
	* BorrowMap: (possibly) zero-copy mutable data structure in a react context
	* =========================================================================
	*
	* The idea behind this concept is that we can have a mutable container in a
	* React-linked store but ONLY IF we never share a reference to the mutable
	* container itself. All the reads must be contained inside selectors. As long
	* as no one has a second reference to the mutable container, then we are sure
	* that no one is able to read/write it without us knowing.
	*

	WAYLAND_PROTOCOLS=/usr/share/wayland-protocols

	# wayland-scanner is a tool which generates C headers and rigging for Wayland
	# protocols, which are specified in XML. wlroots requires you to rig these up
	# to your build system yourself and provide them in the include path.
	xdg-shell-protocol.h:
	wayland-scanner server-header \
	$(WAYLAND_PROTOCOLS)/stable/xdg-shell/xdg-shell.xml $@

	xdg-shell-protocol.c: xdg-shell-protocol.h

	#!/usr/bin/env python3
	import sys
	import json
	import os
	import os.path
	import shutil
	import logging
	import tempfile
	import glob
	import argparse

	/**
	* Flexbox styles so Safari respects position: relative; on the flex item.
	*/

	.flex-box {
	display: flex;
	}

	.flex-item {
	display: flex; /* Fixes Safari issue with position: relative; */