After about a year, on and off, I am veeeery happy to release TWINKLEPLOP, a syntax highlighter of tremendous power! The speed of prism with the customisation of Shiki.

Heeeeeey! Long time no see!

Someone found my work on on.design and reached out. Just a quick commission, nothing huge, but that’s exactly the point. The work gets seen.🫰

im creative with the bugs i create in the code i write 😅

Just ask @Muse to file your claim by sending it this link 😅

🆕: @Meta and @stripe are partnering to make it easy for businesses to accept agentic payments using the @Muse Connector Platform. Learn more: • muse.ai/platform • docs.stripe.com/agentic-comm… • Email jweinstein@ / @jeff_weinstein

Opening access for developers to build Muse connectors. You bring the API -- Muse brings the agent, the browser, and the context of what the person actually wants. People reach your service just by asking for it, and their agent takes it from there. New connectors are live today. Come build with us. muse.ai/platform

Most of these are already true today. Ironically, the SE and PL academics who, theoretically, should be ahead of the curve and show us the way forward, are desperately holding on to the old ways.

> So this morning I decided to plant my flag. Again. I've been writing and talking about all of this for. For many people change is hard to accept. Keep waving the flag!

muse is shockingly good - they nailed the simplicity. it's quickly becoming my go-to for personal AI

I'm working on a new library that enables real shared-memory multithreading for JavaScript, natively. After seeing what's possible with Zig in WASM, I was tired of not having the same possibilities in JavaScript! Here, the main thread and a worker cooperatively increment a counter. The state object is truly shared between the two threads; no messages are ever exchanged after the initial handshake.

The library uses SharedArrayBuffer to achieve this! This feature already provides true shared-memory multithreading to JavaScript, but you can only share raw bytes which is awkward. Therefore, my library is able to serialize every JavaScript value into this buffer and returns wrappers that look and behave like normal JavaScript objects, but really read from and write to this buffer under the hood. Currently, I have support for the following types: numbers, bools, string, boxed primitives, null, undefined, bigint, objects, arrays, Map, Set, Date, TypedArray, DataView, Error, and RegExp. All reference types maintain their identity across the thread boundary. The core engineering challenge is how to best represent these objects in memory so that they still remain fast despite the high dynamism of JavaScript!

🙌🙌🙌 yes!!! love it! @slightlycode was this your doing?

worktrees are such a bad idea. i'm glad we're starting to move out of that world.

2027 prediction: Models will be replacing tons of playwrite tests as a means to crawl and use your application using desktop usage. Just doing it now for Omarchy just shows how crazy powerful it is and how hard it is to do the same thing with scripts.

How do you manage worktrees? I currently don't have a good way to quickly see the list of all worktrees and see the diffs in them. In particular worktrees are automatically created by agents and github desktop requires to add each worktree manually - this is an outdated workflow

Either I'm holding it wrong or concurrent Rust builds are tricky... all of my agents are stepping on each other's toes and are getting blocked