Fun fact, I named it "Stainless" after Stainless Steel pipes, likening ourselves to a high-end plumbing supply shop. If you look at the earliest versions of stainlessapi.com on archive.org, you'll see our original motto was "Quality fittings for your REST API".

All that is to say, the incredibly "boring" infrastructural work of making "boring" APIs like Hubspot's more usefully accessible is absolutely the kind of thing I'm excited to do at Anthropic :)

(It also happens to be what got us all excited to work at stainless in the first place, but of course, we understand it's not for everyone!)

(disclaimer: founder of Stainless and also friends with creator of TypeSpec)

I'm struck by this quote, which I'd be surprised if they could be explained fully by the distraction-reduction mentioned:

> "Evaluation of symptoms on the Parent Global Impressions found that the treatment group at the end of part 2 improved more than the placebo group in part 1 on nearly all symptoms, with statistically significant improvements in GI, receptive language, and average of all symptoms. There were also marginally significant improvements in tantrums, stimming/perseveration, and cognition."

Pretty incredible if true!

They did ;) a highly dynamic one...

I struggle to understand why an Apple lightning cable would be more robust than an Apple thunderbolt cable...

The merits of any project are yours to evaluate.

To me, I see some encouraging thoughtfulness here. However, again, it's true most projects like this don't achieve liftoff.

I'm curious what compilation times are like? Are there theoretical reasons it'd be order of magnitude slower than Go? I assume it does much less than the rust compiler...

Relatedly, I'd be curious to see some of the things from Rust this doesn't include, ideally in the docs. Eg I assume borrow checking, various data types, maybe async etc are intentionally omitted?

Problem: DOM-based text measurement (getBoundingClientRect, offsetHeight) forces synchronous layout reflow. When components independently measure text, each measurement triggers a reflow of the entire document. This creates read/write interleaving that can cost 30ms+ per frame for 500 text blocks.

Solution: two-phase measurement centered around canvas measureText.

prepare(text, font) — segments text via Intl.Segmenter, measures each word via canvas, caches widths, and does one cached DOM calibration read per font when emoji correction is needed. Call once when text first appears.

layout(prepared, maxWidth, lineHeight) — walks cached word widths with pure arithmetic to count lines and compute height. Call on every resize. ~0.0002ms per text.

https://github.com/chenglou/pretext/blob/main/src/layout.ts