This gist summarizes the handleEvent(event) pattern features, something standard, something described by me many times, written in my tiny book, tweeted about, and yet it's something most Web developers ignore.
┌---------------------------------┐
var handler = { | any object that inherits or |
| import { | |
| useReducerWithEffects, | |
| emitEffect, | |
| } from 'react'; | |
| // In a component | |
| const UserComponent = () => { | |
| function fetchUserEffect(id, parentRef) { | |
| const controller = new AbortController(); | |
This is a guide to Vim Script development for Python developers. Sample code for the various expressions, statements, functions and programming constructs is shown in both Python and Vim Script. This is not intended to be a tutorial for developing Vim scripts. It is assumed that the reader is familiar with Python programming.
For an introduction to Vim Script development, refer to usr_41.txt, eval.txt and Learn Vimscript the Hard Way
For a guide similar to this one for JavaScript developers, refer to Vim Script for the JavaScripter
This guide only describes the programming constructs that are present in both Python and Vim. The constructs that are unique to Vim (e.g. autocommands, [key-mapping](https://vimhelp.org/map.txt.html#key-m
The first post has been published: https://www.swyx.io/writing/cloud-distros
The second post has been adapted for Temporal: https://www.swyx.io/why-temporal/
these are bullet points of a blogpost on a topic i know very little about but i feel like there is something there that is happening as we speak
| interface Circle { | |
| type: 'circle'; | |
| radius: number; | |
| } | |
| interface Square { | |
| type: 'square'; | |
| width: number; | |
| } |
| Mute these words in your settings here: https://twitter.com/settings/muted_keywords | |
| ActivityTweet | |
| generic_activity_highlights | |
| generic_activity_momentsbreaking | |
| RankedOrganicTweet | |
| suggest_activity | |
| suggest_activity_feed | |
| suggest_activity_highlights | |
| suggest_activity_tweet |
| module.exports = function arrayIncludes(arr, search, fromIndex) { | |
| return arr.includes(search, fromIndex); | |
| }; |
This is an example of a script for new systems, which 'mounts' dotfiles from a cloud-synced directory, and also moves junk out of the homedir into the places where it "should" live as per various filesystem standards (Linux FHS, FreeDesktop.org, macOS, etc.), replacing the origins with symlinks to the new locations.
The script is designed to be idempotent; it could theoretically be run on startup.
Various locations are hard-coded. Please take this script only as inspiration; don't try to run it directly.
Bash expects just a few files in your homedir, but is fine with these files
being symlinks. As such, I instead create a subdir, ~/.bash, and then symlink
~/.bashrc to ~/.bash/bashrc and ~/.bash_profile to ~/.bash/bash_profile. This
gives you a new namespace (the ~/.bash dir) to pollute with little files, which we're
going to do plenty of below.
It's great for beginners. Then it turns into a mess.
