Pinned
~paul
~paul
@paulvall.dev
generalist 🇲🇽 | guac enjoyer 🥑 | be kind to each other ✌🏻 | @astro.build @bomb.sh @e18e.dev @studiocms.dev @tauri.app
258 followers149 following703 posts
after running some tiny perf browser tests, i can say that helium is goated. awesome job @wukko.me
~paul reposted
hey! did you know we have an open collective? we do! and now it's on our @bsky.app profile, too 👉 bomb.sh/donate
~paul reposted
One of my favorite things about the new @bomb.sh router is how well it scales. It doesn't matter if you have single entry point or a hundred.
our new CLI router supports standard schema and takes lots of inspiration from HTTP. read all about it the blog!
~paul reposted
👀 Introduce pulls.review Categorize changes in Pull Requests into logical groups, with a summary. Helps you do reviews more efficiently by focusing on what matters. Everything runs in your browser. With opt-in GitHub userscript, GitHub Actions, or CLI for local git changes!
i'm sold on upm, gonna start using it 👀
upm does win on cold! raw.githubusercontent.com/unjs/upm/mai... Also in warm at least in limited benchs raw.githubusercontent.com/unjs/upm/mai... We really don’t need more size to be faster. Actually little warm startup cost is because Node has to bootstrap ~50MB logic
à l'époque où on était encore sur twitter
~paul reposted
jumping on the opus 5.5 video bandwagon with a @bomb.sh promo this was a one-shot prompt and it pulled that sick logo animation out of thin air 🫠
built a claude code plugin around typesafe's jev, the new model that returns probabilities instead of prose jev-shadow asks it 5 hazard questions about every command claude proposes and logs the answers next to what claude code's own classifier decided. zero latency, changes nothing
understanding is the one part of software that still runs at human speed. that's not a bottleneck. that's where we're still needed. i wrote about why open source gets to choose its own pace.
this post is better because the power team at @e18e.dev reviewed it before hand. grateful for these peeps roasting my stuff 💜
@bomb.sh clack 1.8.0 is out 🎉 your validate() can be async now, tab completes paths in path(), and CANCEL_SYMBOL is finally exported. changelog here github.com/bombshell-de...
alex has been doing an amazing job working on this for the past months 🫡
The @e18e.dev framework tracker is nearing an official release. We have worked hard to include a wide array of stats on meta-framework performance, including data from HTTP Archive. See below for a sneak peek at the percentage of sites in each framework that meet the benchmark. 🧵
in january 2025 nate invited me to contribute to contribute to @bomb.sh back then clack was doing around 2 million weekly downloads. this week it crossed 19.3 million. almost 20 million. i keep thinking about why.
and thank you @43081j.com , who i’ve worked with hand in hand this whole time. his work on release cadence, bug fixes, and shipping features has been crucial to getting clack here.
in january 2025 nate invited me to contribute to contribute to @bomb.sh back then clack was doing around 2 million weekly downloads. this week it crossed 19.3 million. almost 20 million. i keep thinking about why.
clack wouldn’t be where it is without the people i work with. thank you @natemoo.re for the inv and trusting me to help maintain the project.
in january 2025 nate invited me to contribute to contribute to @bomb.sh back then clack was doing around 2 million weekly downloads. this week it crossed 19.3 million. almost 20 million. i keep thinking about why.
in january 2025 nate invited me to contribute to contribute to @bomb.sh back then clack was doing around 2 million weekly downloads. this week it crossed 19.3 million. almost 20 million. i keep thinking about why.