GP seemed to be commenting on the Trump administration, not necessarily individuals of conservative persuasion. The Trump administration diverges materially from traditional conservative doctrine in many ways.
> ... and their team is joining Anthropic to build, who knows, some dumb integration to make Hubspot data available in Claude, or something equally as boring.
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!)
Hmm, that's one explanation, but I'm curious what leads you to believe it's the correct one?
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."
> Prior to the study, 83% of participants had "severe" autism. Two years later, only 17% were rated as severe, 39% as mild or moderate, and incredibly, 44% were below the cut-off for mild ASD.
It's possible that use of `contenteditable` and ability to save the file could help but that has a lot of limitations/gotchas, so I'm inclined to agree.
I've been very curious about that too. I wonder if it's actually much better at admitting when it doesn't know something, because it thinks it's a "dumber model". But I haven't played with this at all myself.
This seems awesome. Seems to address many of my armchair complaints about both Go (inexpensive) and Rust (bloated/complex).
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.