Lesson learned: if you want Cloudflare to serve Brotli-compressed content, disable gzip in nginx for those assets.
Cloudflare won't re-compress what your origin already gzipped, it just forwards the gzip. Send it raw & CF brotlis it. 50KB → 40KB. ⚡
https://t.co/BLsQo3Q4DU
We just dropped a little teaser for an upcoming film...
The film tells the story of PHP, a language that was never meant to become what it is today, told by the people who shaped it.
Expect the full film later this year.
https://t.co/7hzt744l8l
Featuring:
Nils Adermann (Composer) @naderman
Taylor Otwell (Laravel) @taylorotwell@laravelphp
Nikita Popov (PHP Core) @nikita_ppv
Fabien Potencier (Symfony) @fabpot@symfony
Roman Pronskiy (The PHP Foundation) @pronskiy@ThePHPF
Brent Roose (JetBrains) @brendt_gd@phpstorm@jetbrains
....and more....
@jetbrains is supporting us to make this film. Thanks to the team there!
Lesson learned: If you're using Laravel Scout you may be reindexing significantly more than you expect by default
By default, any $model->save() will *always* issue a reindex on the model, because Scout listens for the Eloquent "Saved" event and doesn't check if the model had any changes
For example, if a user saves a Post and makes no changes -- Scout will reindex the model anyway
This can turn into *massive* search indexing queue churn at scale across all your searchable models unless you explicitly guard against it by only allowing a reindex when attributes you're indexing are changed:
i still hate reply bots and wish they'd go away
but damn one made an interesting point today that i felt compelled to reply to
99.999% of them are still garbage and you are garbage if you use them
So I’ve compressed and condensed loops. I’ve bent it. My first loop runs from 6:00 a.m. to noon, and I’m not crazy. You’re crazy for thinking it takes 24 hours to loop just like some dude in a cave did 300 years ago. My second loop starts at noon and goes till 6 p.m. That’s loop two. And then the next loop is 6 p.m. to midnight. What I’ve done now is I have changed and manipulated loops. I now get 21 loops a week. Stack that up over a month and I’m gonna kick your butt.
if you’re still writing loops that prompt coding agents you’re falling behind. you need to build a meta agent that infers what loops you would have wanted based on your vibe and then write those loops
Every time someone ends a meeting with "I'll give you a few minutes back," I deposit those minutes into an interest-bearing account. Today I hit meeting Coast FIRE. I can decline every meeting from now on and still retire on time.
I have to push back on 2 things as i think one is categorically incorrect and the other is demonstrably incorrect.
1. Debugging:
Debugging is not a thing if coding is solved. You would produce correct behaviors. I don't understand how a solved problem could produce erroneous behavior.
2. Coding is the easy part:
setting hardware, capacity, talking to users, product planning agreed is in fact hard, but so is coding.
Example: If coding was in fact not hard then Claude Code having a flickering issue for well over 9 months, which is a purely software challenge, would have been solved almost immediately (immediately being on a shortened time scale comparatively to a human solve time scale).
For more trivial applications software approximation can largely work. I also love software approximation for exploring how things should feel.
Discovered a new method for detecting if someone is using Incognito in Chrome:
Write 512 tiny 1-byte responses into a scratch Cache API cache, then read:
https://t.co/gsVNLl57y6.estimate().usageDetails.caches
Normal Chrome: ~393kb
Incognito: ~85kb
Why? When you're in incognito, Chrome writes to memory instead of disk, which leaves less metadata residue
I've left most of what I want to say in the VoidZero blog post. But worth repeating:
Thank you @voidzerodev team for trusting me and joining me on this wild ride. I am very proud to have assembled such a talented team and even prouder of what we have built together.
Thank you all our investors for believing in my vision, in particular @caseyaylward from @Accel who led both our Seed and Series A.
Thank you the @vite_js community. Vite and VoidZero wouldn’t have come this far without your trust and support. We will continue building with all of you, together, in the open.
And thank you to everyone that made this happen at @Cloudflare. Looking forward to working with you all!
https://t.co/0ly53VCOSr
Hey @1Password A family member deleted our whole family account, thinking they were only deleting their account. All my personal passwords/passkeys are there, so I’m pretty screwed. Support has not answered me for several hours. I need to recover access ASAP. Please advise