Jacob

worst engineer at the company, third coolest… created bootstrap 300 years ago… now building things at the Pierre Computer Company.

[Jacob @fat]

Signups are now open on Code[dot]Storage.

Today, more new repos are created per second on Code Storage than any other platform.

Lovable, Bolt, Amp, Poke, and many more of the largest agentic workloads store their code and agent memory at scale using https://t.co/oJLq0faUTg.

[Libbie Frost @Libbiefrost]

Jacob Thornton (@fat) is the founder of Pierre Computer Company (@pierrecomputer).

Pierre provides the building blocks of the computers that agents will use to do work. But Pierre is as much a brand and culture project as an infrastructure one. Jacob believes brand is the most important thing you can be doing in 2026, and his references run from MTV and skateboard brands to Godard films and the magazine racks at sf Heath newsstand.

In this interview, we talked about why MVP culture is cringe, how to find and hire obsessives, why the best creative work at Pierre starts in iMessage threads, and the real reason the company is named Pierre… sort of.

Read the full interview "Virtual computers for agents, chrome blobs, and MTV" linked in the thread.

cc @thisisrayouf

[🎨 @devinjacoviello]

After no consideration, @narrowd and I have joined our friend @fat at the pierre computer company.

To celebrate this union, we have resurrected the commemorative flaming eyeball website.

[Shu @shuding]

Optimized https://t.co/ELWO2Qtu0J to be 3.8x faster: 850ms → 221ms. It's still far behind @pierrecomputer's https://t.co/Ft4edFyyZX (incredible work!)

Also wrote down some thoughts on https://t.co/FW2Hu9LDtL

[Luke Parker @LukeParkerDev]

HOW DO THEY KEEP DOING IT????????????
adding to OC Desktop rn.

[Jacob @fat]

@Lermatroid 😂😂

[Jacob @fat]

@steveruizok @superlogical "excuse me, yes, have you seen the website. i'm on there."

[Jacob @fat]

@feedthejim ( O_O )

[Jacob @fat]

Highlights by the Pierre Computer Company.

A new library for highlighting your diffs and code.

Written in web assembly text.

70 languages, ~300x faster than Shiki.

You can read more about it here (https://t.co/j52oU5b6Ho)

[Jacob @fat]

@viccsmind hahahaha there you go

[Jacob @fat]

@viccsmind you click the header?

[Jacob @fat]

@wwwjim 🙏🙏🙏

[khoiracle @khoiracle]

Migrated supaterm to highlight immediately, 20x speed up. So good

[Jacob @fat]

Not sure if this exactly answers the question:

> "Writing it by hand means working directly with loads, stores, branches, and vector operations. Which isn't the most fun…

Rust and Zig can both compile to WebAssembly and provide control over memory and SIMD.

However, our preference for WAT is about the workflow: the source expresses the loads, comparisons, and branches we want to inspect and tune.

For example, the 16-byte comment scan is written directly as a vector load, comparisons, and a bit-mask check. With a program built mostly from scans like this, working in that instruction representation is useful. The choice also gives us more details to maintain ourselves."

but sure @jexia_ could weigh in with more information if not!

https://t.co/j52oU5b6Ho

[Lucas Meijer @lucasmeijer]

everything these guys do is so good! I migrated AgentsInTheCloud to Highlights, and everything syntax highlighting got a lot faster!

[Jacob @fat]

@icyphox 👀👀

[Jacob @fat]

@zack_overflow also you can play with the header thing now

[Shu @shuding]

@fat @jexia_ Masterpiece @jexia_

[Jacob @fat]

@VrianCao @pierrecomputer 🙏🙏

[Andrew Reed @andrew__reed]

@fat

[Jacob @fat]

@zebriez 🙂‍↔️🙂‍↔️

[Ray Arayilakath ‎.߆ @rayhanadev]

written in webassembly text is diabolical work this is so cool