const MEMORY_SIZE = 1_000_000; | |
type Memory = any[] | |
type registerName = 'stackPointer' | |
| 'instructionPointer' | |
| 'returnValue' | |
| 'general'; | |
interface Processor { | |
halted: boolean; |
I'm making a replacement for this at some point, just note that some keys probably don't work (and if so, not for more than 30 days max).
These keys have been tested to work. These are a combination of keys from Chinese websites, trial keys inside ISO's, auto-activate keys in OEM ISO's, and directly from Microsoft's website, all aggregated for your convenience.
In order to use these keys, you need the right edition of Windows XP/2003. Not just Home/Pro/Enteprise/etc, whether it's a Retail, OEM or Volume version. There's a clear cut way to check this.
If you see this, you have a Retail copy.
// segments are all of the segments in all of the shapes in the scene | |
// point is light point | |
// viewport is top left, top right, bottom right, bottom left | |
function getVisibilityPolygon(segments: Segment[], point: Point, viewport: Point[]) { | |
const brokenSegments: Segment[] = [] | |
const viewportMinCorner = viewport[0] | |
const viewportMaxCorner = viewport[2] |
a thread where we can discuss some crazy routing ideas a bit out in the open branching out from the previous discussion on filesystem routes over at: https://discord.com/channels/815937377888632913/1014946079965454366
so, first of all, it seems there is a close alignment between how vite-plugin-ssr and router5 handles routing:
- vps: (
view === 'overview'
) @ https://vite-plugin-ssr.com/layouts#nested-layouts - router5 (
route === 'dashboard'
) @ https://youtu.be/hblXdstrAg0?t=197 maybe with the small exception that router5 has the explicit perspective of routes as app state whereas I didn't get the impression from vps that it's viewed as such (even though it technically is still state).
I recommend watching this router5 talk from 2:45 - 7:50 https://youtu.be/hblXdstrAg0?t=165 since it's really key to how I think about view / state separation, and I think of routing as a state separate from the view. (After all, and especially in a client-rendered app, what page it is showing is certainly a major part
import { Prisma, PrismaClient } from '@prisma/client'; | |
import { exec } from 'child_process'; | |
import * as util from 'util'; | |
const execPromisify = util.promisify(exec); | |
const prisma = new PrismaClient(); | |
const tables = Prisma.dmmf.datamodel.models | |
.map((model) => model.dbName) | |
.filter((table) => table); |
### | |
### [2023-06-19] UPDATE: Just tried to use my instructions again on a fresh install and it failed in a number of places. | |
###. Not sure if I'll update this gist (though I realise it seems to still have some traffic), but here's a list of | |
###. things to watch out for: | |
### - Check out the `nix-darwin` instructions, as they have changed. | |
### - There's a home manager gotcha https://github.com/nix-community/home-manager/issues/4026 | |
### | |
# I found some good resources but they seem to do a bit too much (maybe from a time when there were more bugs). | |
# So here's a minimal Gist which worked for me as an install on a new M1 Pro. |
https://github.com/spieglt/cloaker - password-based file encryptor (NOTE: uses Qt)
https://github.com/str4d/rage - file encryption tool and librarary that uses the age format
https://github.com/mohanson/gameboy - gameboy emulator
https://github.com/bartwillems/lyriek - fetch the lyrics of a song playing in an mpris-compatible player
https://github.com/JakeStanger/mpd-discord-rpc - discordrpc for mpd
package main | |
import ( | |
"context" | |
"database/sql" | |
"fmt" | |
"io" | |
"log" | |
"math/rand" | |
"net/http" |
This September I decided to share my laser printer so anyone on the internet could send me printed messages.
Within a few days I got hundreds of fun print-outs from people all over the world.
Using Google Cloud Print, you can easily make your printer public too. Here's how to do it: