76 karma · joined May 2, 2026
I came across a line in the Social Contract that caught my attention: “The platforms that dominate today have drifted from their original promise. Feeds are flooded with content from accounts no one follows.”
I respectfully disagree with that. IMO the problem lies in the opposite direction. The content we see on these sites is driven by algorithms that reward popular posts and influencers. This creates a system of “stars” and “fans,” which does not foster genuine connections.
The original internet promised to give equal voices to all and allow users to see things they might otherwise miss. When I encounter a new social network like yours, especially one as elegant as this, I secretly hope it will restore that original promise.
I’m glad that you’re trying the Layoutmaster library in your projects. You can also feed it video with a predominantly white background (or any other solid color). Additionally, the video can contain multiple objects, and the algorithm treats them uniformly.
"What's the point?" she asked.
I said, "You can click it."
"But what's the big deal?" she was baffled.
"You can click it,“ I said.
“That's the big deal."
Author here.
Tools like Pretext help you avoid DOM reflow by measuring texts without the DOM and returns the height.
Layoutmaster does that too, but it goes beyond a simple measurer and solves the full layout with a real layout engine that’s as fast and as capable as the browser itself. It then hands you the solved layout via “pieces” — fragments with exact coordinates, baselines, and paint metadata for you to easily and precisely recreate the layout in HTML, canvas, or WebGL.
The APIs are stateless and extremely simple, yet they answer all your layout questions. Enamored by the “animated dragon swimming through texts” demo from Pretext? You can easily create that with just a few lines of code instead of hundreds.
form() Given a width, how does this lay out and how tall does it get? No DOM. No rendering. Just pieces.
fit() Given a bounded box, what fits and what overflows? Every character accounted for. Nothing disappears quietly.
plan() Parse once, never re-measure. The same plan drives form(), fit(), and flow() without repeating any work. The Book Masonry demo runs on this.
flow() Content does not always fit in one box. flow() carries text through multiple regions — columns, panels, spreads.
pour() Not every surface is a rectangle. Fill any shape — a circle, a polygon, an image silhouette, a video frame.
produce() Hand it a document. Get back pages. Publishing-grade pagination.
My first experiment was to wrap it in a set of APIs called Layoutmaster. They work natively with the browser’s text systems to bypass DOM overflow. It was very fast... faster than the browser in many cases. This made me wonder if it would be faster in Rust so I made a port just for fun.
Turns out, the TS version was fast -- over a thousand pages per second, but the Rust version is quite a bit faster. It's still not fully optimized though. Still working on it.
I have no intention to use it for document generation unless there is a demand for it. For now I’m more interested in how this native engine can help with frontend jobs like creating a native live-editing surface without a browser.