Tony Sullivan

Family Fued question: > Name something you'd hate to be on when it breaks down. "Toilet" should have been the number 1 answer. That it didn't even make the list is mind boggling. Has no one ever seen the aftermath of a sewer backup?

Fine-grained reactivity driven by the server has been really interesting so far. It's a tight needle to thread, but when the server knows what's rendered on the client and can send tiny HTML patches when state changes, you stop worrying about cache invalidation. There's no client copy to go stale.

Confirmed: version numbers really are cheap 🏷️ #StatorJS 2.5 is out 🚀 five minors since 2.0. Each one small, but together they round out what production apps need: real security primitives, first-party middleware, and a CLI that owns the toolchain. statorjs.dev

working with @frontside.com (@cogentdude.com and @jacobbolda.com) on this rendering engine has been stellar, and i'm thrilled they've joined the @bomb.sh core team. better together! tty is a smaller, faster, more powerful terminal rendering engine, and it's just the start bomb.sh/docs/tty

🌶️ Server components don't have to be hard. It really doesn't have to be a big deal. Client code goes in a <script>. Period. No "use client;" pragma. No "/client" imports. No debating whether to "useServerProps". Browsers know <script>'s. Put client stuff there. @statorjs.dev #webdev #StatorJS

"Synergy, bitches" - Russ Hanneman Silicon Valley and Mike Judge strike again @statorjs.dev `create stator` is powered by @bomb.sh #StatorJS CI is powered by changesets ...changesets is now powered by @bomb.sh Should we all be passing around the same fictitious $100b and going public?

#sdd must mean shitpost driven development, right? Specs be damned.

Its not every day you find a compiler bug when taking a screenshot for a shitpost 🙃 #StatorJS #webdev

Stator 2.0 is out 🎉 🌶️ We removed two-way binding read() is now the only display primitive. Its the same in a server template or a client island - the compiler picks the right mechanism for each. Writes are typed events that machines declares and the compiler checks statorjs.dev #StatorJS #webdev

Stator 1.7 is out 🚀 Stator renders your pages on the server, straight from the state machines that hold your logic. As of today those same machines can serve your JSON API, your RSS feed, and anything else that speaks HTTP. No second data layer, nothing to keep in sync. statorjs.dev

3 minors in 4 days? A wise soul once told me that version numbers are cheap 🧠💸 #StatorJS #webdev #semver

@paw.pulsr.social this one's partly yours - the Stator docs now open with an intro focused the thing we talked about: keeping the page matching your database. Thanks for the feedback on Stator's launch post! docs.statorjs.dev/introduction/the-simple-version

Your data lives in a database on the server. Stator's bet: render the page there too. When data changes the browser gets a tiny note, "change this bit", instead of a whole app asking the server what's true. One program. No glue code to break. statorjs.dev #buildinpublic #webdev #StatorJS

Stator 1.4 is out 🎉 Stator keeps your app state on the server — the browser just gets tiny DOM patches. New: defer() for slow APIs — fetches run in parallel and the page arrives complete. And live lists that update one field at a time. statorjs.dev #StatorJS #webdev

if any of said open source communities or atproto companies would like to have someone design merch + manage a shop while funding an ecomm-on-atproto experiment, my dms are open! ideal partners would have deep open source roots, believe atproto is the future, and want rad, gender-inclusive merch ✌️

This round of attacks on Iran sure look more focused on what you do to soften defenses before a land invasion. Here's hoping I'm totally wrong on that one...

Hello, World. We're building Stator — fine-grained reactivity that lives on the server. State machines hold your logic. Every event patches just the DOM that changed. No client app state (unless you really need it). Docs and demo are live: statorjs.dev #buildinpublic #webdev #StatorJS

I'm always confused by Trump's claim that he didn't lose in 2020. If he won in both 2016 and 2020, doesn't that mean he is ineligible to be the President *now*?

StatorJS is the first major project I've used @chisel.build with for long term planning Its been a huge help so far especially tracking long term specs. Using md right in the repo as the roadmap, feature spec, and "why" behind the feature is more handy than I expected github.com/statorjs/stator/

Continue to be impressed with @bomb.sh Building a new `create-stator` CLI, ~200 lines of code for a for a full featured dev bootstrapping experience 🔥 github.com/statorjs/sta...

You'd think I would have learned that building an entire framework is a ton of work, but chipping away at statorjs.dev is finally starting to bear fruit I'm finally at the point of building an LSP and VSCode(ium) plugin, volarjs.dev is still a huge help on that front

I've seen more and more complaints over how aggressively web scrapers are hitting sites today Part of the challenge is them having to scrape rendered HTML. XML + XSLT would have made this a lot cheaper to manage 🔗 tonysull.co/posts/i-ve-s...

I'm not sure where the #llm ends and the harness begins. Arguments that LLMs are just stochastic parrots or fancy auto complete still make sense. But given what they can do today, that must mean a well managed parrot (via the harness) can do some impressive stuff. 🔗 tonysull.co/posts/i-m-no...

New overcommitted is out 🎧 Adam Argyle (@nerdy.dev) on going from seven years at google chrome to staff design engineer at shopify, why llms suck at css, and why he thinks "the finishers", design engineers, are one of the most ai-proof roles in tech right now overcommitted.dev/design-engin...