
Making a programming language - BAML. @boundaryml, 🦄 aitw podcast: https://xitter.cf/t.co/g4CJWgP0gR prev YC, google, msft, deshaw, and other things
Seattle, WA
Joined September 2012
- Tweets1.5K
- Following565
- Followers3.6K
- Likes1.3K
Slop is code you dont read. And better models means more slop.
the solution? write sloppy tools to build stable systems.
but for the most committed people, go build new foundational systems. Rebuild github, rebuild tmux, rebuild database, and yes rebuild programming languages.
Big thanks to @swyx and the whole community for having us out at @aiDotEngineer
“OpenAI worse than jev 🤡” feels like what they used to say about anthropic vs OpenAI
I benchmarked "Jev-killer" OpenAI Decisions API against Jev for HiringCafe.com, serving 2.5 million users. The task is to predict how relevant a user query/resume is to a job description, on a scale of 1-10. OpenAI is 2x more expensive and 5-10% worse. 🧵
Replying to @twistin456
what are questions you want to be able to ask?
Vaibhav Gupta retweeted
Everyone in AI is building for everyone else in AI.
We're building for your group chat.
Introducing Charming ✨ Personal apps for us normies.
Make an app for your book club, a meal planner for your family, go wild (it's free!)
Build in Claude/ChatGPT, share like a Google Doc
what if you could ask a program any questions about itself as it was running?
coming to all baml programs near you 🐑
Replying to @codeshaunted
@codeshaunted just converted me to: terse
good bye to @dillon_mulroy's /bro skill. we had a good run 🥲
Replying to @JamesWard
People that like go’s error handling haven’t had to write a system that needs to be fault tolerant 😅
Now go’s concurrency? That’s beautiful.
Vaibhav Gupta retweeted
if only someone were building a programming language for this new era
Guillermo Rauch@rauchgOct 4United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
DHH is fundamentally right about Rust. For context, Vercel has been undergoing a Rust-ification (carcinization, technically 🦀) for a while.
One of the first projects we migrated was Turborepo, from Go to Rust¹. The migration completed, but the RoI was actually quite controversial internally.
While Rust was in our eyes better for low-level OS access, something crucial for a build system like Turbo, the human migration costs were very sustantive.
Go is very fast. It's beautifully designed. It's easy to iterate on. We were very conflicted about the migration, because it was *humans* writing the code, *even if we knew Rust was a better choice*.
The calculus has now changed. What's "best for humans" is no longer necessarily "best for business".
FWIW, it's also quite unlikely that Rust is the end-all-be-all toolchain. I'm quite certain there's greener pasture ahead, because Rust itself was designed before the 'supersonic tsunami' of agents hit.
¹ https://vercel.com/blog/how-turborepo-is-porting-from-go-to-rust
why would you not have a faster app if you could? 🦀
Replying to @dhh
Again, I'm not saying that all apps need Rust levels of performance. Far, far from it! But I am saying that if agents are really good at writing Rust, and you're onboard with agent acceleration meaning we don't read all generated lines, then it's a good argument for Rust!
Replying to @NatureBlueee
yea it helps. sometimes if its big i'll queue multiple double checks
Replying to @realamlug
i mean don't get me wrong, v8 is a beautiful piece of engineering.
but i dislike a few of the semantics deeply baked in js. null vs undefined for example.
its also got some amazing parts though, unions and anonymous records truly made web dev possible











