Web app technique I’m considering: decks/ flash-cards.md flash-cards.json App stores state in JSON file: • Pro: Syncing state between devices via file system • Con: User must select directory first (via OS), deck second (via app). Why? So that the app can write a sibling file to the directory.
Upcoming Node.js feature: Package import specifiers (*) can start with #/ "imports": { "#/*": "./*" } Why is this useful? Gives you more naming options. Previous solution (e.g.): "#root/*" (*) #NodeJS #JavaScript
Tiny UI detail in Visual Studio Code: If you select matches via Command-D (Windows: Control-D) then selecting doesn’t stop at the last match, it wraps around and stops where everything started. That makes a big difference because you see the initial context while making changes.
20 years ago today (1995-12-04): “Netscape and Sun announce JavaScript, the open, cross-platform object scripting language for enterprise networks and the internet” #JavaScript
RE: It’s amazing how quickly the Go version of TypeScript was created. The key “trick” of the TS team was to port, not to rewrite: View quoted note →
JavaScript—matching at a given index inside a string (useful for parsing/tokenizing): • .startsWith(), .endsWith(): • .indexOf(), .lastIndexOf(): • RegExp /y and /g with .lastIndex:
Random foldable phone idea: Make the outer display e-ink.
I’m surprised that this is legal: “our AI Biden avatar gives you speeches, interviews, analysis, and viral moments”
RE: #Mastodon: I like that you stay within your server’s web app if you click on a quoted post. Combined with all replies being fetched on demand, it means that you almost never have to visit other servers.
Interesting warning label image