Dmitry N. Medvedev Dmitry-N-Medvedev

Personal notes building zig 0.15.0-dev.xxxx on Macbook M3 Max

20250407 Sequoia 15.4, latest XCode Commandline Tools, homebrew-installed LLVM 20.1.2 (llvm@20)

This way of building probably works on all Apple Silicon Macs, but you must check other models yourself. Some Intel Macs should also work (the only significant difference is the default homebrew path). But I don't test that anymore.

Here is a list of earlier M3 Max builds

Autoscaling SVG's

Scaling svgs is annoying and most solutions require tradoffs I don't want. I'm suprised the ammount of solutions out there that are pretty subpar or require extra overhead.

What I don't want:

use an image tag
use wrappers
use weird padding
pass down props for width/height or viewBox props.

I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.

But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.

Svelte is a language.

Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?

A few projects that have answered this question:

As the number of different possible states and transitions between states in a user interface grows, managing styles and animations can quickly become complicated. Even a simple login form has many different "user flows":

https://codepen.io/davidkpiano/pen/WKvPBP

State machines are an excellent pattern for managing state transitions in user interfaces in an intuitive, declarative way. We've been using them a lot on the Keyframers as a way to simplify otherwise complex animations and user flows, like the one above.

So, what is a state machine? Sounds technical, right? It’s actually more simple and intuitive than you might think. (Don’t look at Wikipedia just yet… trust me.)

Let’s approach this from an animation perspective. Suppose you’re creating a loading animation, which can be in only one of four states at any given time:

Here's an example of how to debug Mocha v4 if it hangs.

Ensure you're using a Node.js 8 or newer (or any version with async_hooks support).

If you run your test, you'll notice it hangs:

$ mocha test.js

Here's an example of how to debug Mocha v4 if it hangs.

Ensure you're using a Node.js 8 or newer (or any version with async_hooks support).

If you run your test, you'll notice it hangs:

$ mocha test.js

	import { build, files, version } from '$service-worker';

	// https://github.com/microsoft/TypeScript/issues/11781 - this is needed for TS and ESLint

	/// env serviceworker
	const globalThis = /** @type {unknown} */ (self);
	/// <reference no-default-lib="true"/>
	/// <reference lib="es2020" />
	/// <reference lib="WebWorker" />
	const sw = /** @type {ServiceWorkerGlobalScope & typeof globalThis} */ (globalThis);

	// ==UserScript==
	// @name document.load client injection
	// @namespace http://tampermonkey.net/
	// @version 0.1
	// @description The Avocent PM1000/2000/3000 PDU runs an old JavaScript interface that relies on the XMLDocument.fetch() function that has been removed. Emulate this.
	// @description inject the document.load implementation into real page context.
	// @author Andreas Thienemann <[email protected]>, based on a script from [email protected], based on idea from [email protected]
	// @match http://172.16.10.64/*
	// @match http://172.16.10.65/*
	// @run-at document-start

	<div class="canvas">
	<div id="totalCounter" class="total-counter"></div>

	<div id="clap" class="clap-container">
	<i class="clap-icon fa fa-hand-paper-o"></i>
	</div>

	<div id="clicker" class="click-counter">
	<span class="counter"></span>
	</div>

	[Unit]
	Description=Redis In-Memory Data Store
	After=network.target

	[Service]
	Type=forking
	User=redis
	Group=redis
	ExecStart=/usr/local/bin/redis-server /etc/redis/6379.conf
	ExecStop=/usr/local/bin/redis-cli shutdown