just you wait and see! Rust devs won't be laughing when Rust gets rewritten in Rust. won't be so funny, then, will it!?!
David is as good as it gets. the toppest of top talent. he ships aggressively (just look at ArkType!), innovates (attest), and takes on challenges many others would never have the bravery to even prompt an agent for (ArkRegex).
I'm looking for my next role 👀
TS SDKs, DX, agent tooling. remote/hybrid from Boston.
if you've enjoyed ArkType, Standard Schema or my TypeScript perf work, a repost would mean a ton 🙏
ssalbdivad.com
Replying to @fernandorojo @vercel
awaiting the rust rewrite!
Replying to @no237s5
that's a great line - gonna steal that one!
URGENT NOTICE: Congratulations, you have been randomly selected to receive a 100% FREE VIP Lifetime Membership to the MiTS exclusive Discord, simply reply with your full name and mother’s maiden name within the next 10 minutes to claim your prize!
so what was the point, then? well. if you don't get it.. not gonna even try at this juncture to overcome the twitter-rage defending tw. if you make great products with tailwind: genuine thumbsup to you, seriously. keep shippin. but maybe also take a peek at what you ship?
but the point wasn't about users.. it's interesting to see that some people intuitively understand what's bad about (to phrase it more precisely than the original tweet) _elements having kilobyte-scale classNames_. it's not about gzip/class caching/network tab
furthermore, @vercel is owed an apology. the point was more about tailwind than v0 - but clearly people didn't take it that way. Vercel obvi makes top tier user experiences. period. and as the peanut gallery did a great job of illustrating, users probably aren't affected much.
to all the "this was working as intended!" people.. @vercel fixed it. good luck squaring that circle.
🤣fun fact: @vercel's @v0 ships over a kilobyte of @tailwindcss for every button on every page (and has for over a year)...




