1.1. Board Setup
- The board must be square: standard sizes are 3×3, 4×4, 5×5, 6×6, 7x7, or 8×8.
- The board starts empty.
- Players each have a supply of stones and capstones based on board size:
# Block everything in search results except actual results & videos: | |
www.google.com###search div>div[data-rpos]:not(:has([data-snf])):not(:has([data-vurl])):not(:has(h3>a.l)):not(:has([jscontroller]):has([data-maindata*="currency"])) | |
# AI overview: | |
www.google.com##[data-mcpr] | |
# Junk below search results: | |
www.google.com###bres | |
# Junk in right-hand column: |
#!/bin/bash | |
set -euo pipefail | |
$REPO_DIR=~/devel | |
repos="1password bitwarden dashlane lastpass opvault passwordbox roboform stickypassword truekey zoho-vault" | |
# pull all repos | |
( | |
for repo in $repos; do | |
echo $repo |
These are my GNOME extension settings to make the Ubuntu desktop work mostly like Windows 8/10 used to work:
CTRL
(Tiling Shell)WIN + .
(Emoji Copy)between the most popular frontend frameworks (React, Svelte and Solid in particular) what are the features a modern frontend framework must have to be considered a serious option? focus on frontend frameworks with fine grained reactivity. ignore features like server side rendering and server components and focus on frontend features. identify features and requirements that are handled differently in each framework and focus on the problems they solve.
To be considered a serious modern frontend framework with fine-grained reactivity, the following features and capabilities are essential. These features address core challenges like efficient DOM updates, state synchronization, and developer ergonomics. Below is a breakdown of these requirements and how React, Svelte, and Solid handle them differently:
A framework must track dependencies at the most granular level (e.g., individual variables or DOM nodes) to update only what changes, avoiding
const DANISH = { | |
"Hello {{name}}!": "Hej {{name}}", | |
"Welcome to the world": "Velkommen til Verden", | |
"You have {{amount}} {{cookies}}": "Du har {{amount}} {{cookies}}", | |
"cookie": "kage", | |
"cookies": "kager", | |
"Missing translation": "Manglende oversættelse", | |
} | |
type TranslationKey = keyof typeof DANISH |
const fs = require('fs'); | |
const path = require('path'); | |
const TurndownService = require('turndown'); | |
// Directories | |
const inputDir = path.join(__dirname, 'html'); | |
const outputDir = path.join(__dirname, 'markdown'); | |
// Initialize Turndown | |
const turndownService = new TurndownService({ |
Claude.ai just helped me make a whole lot more sense of the absolute mess that is BNF-family syntaxes. 🤔
I just discovered ABNF is actually a standard, RFC 4234.
Why isn't this more widely used?
BNF in the wild drives me nuts - no two grammars are ever written in the same flavor of BNF, and often grammars are published as merely "BFN" neglecting to even specify which BNF variant was used.
Are there any other BNF variants that are properly standardized?
I want you to quiz me in my knowledge of biases, using the following method:
Below is a list of biases I'd like you to quiz me on:
div#tabs-tabbar-container { | |
padding-top: 5px !important; | |
height: 34px !important; | |
} | |
div#header { | |
min-height: calc(40px / var(--uiZoomLevel)) !important; | |
} | |
.button-toolbar.workspace-popup.tabbar-workspace-button.button-menu { |