Laravel 13.20+ finally brings first-party image processing. ๐ผ๏ธ
Huge shout-out to @enunomaduro for cooking this one.
$request->image(), Storage::image(), configurable drivers, and immutable transformations.
This feels like it has always belonged in Laravel.
๐ตโ๐ซ At Oh Dear, we ran into a tricky DNS edge case while improving our monitoring. My colleague Mattias did a great job digging ๐ฅ into it and wrote up both the problem and how we're addressing it
The gist: A domain can be removed from a registry and still appear healthy to uptime checkers for days, because recursive resolvers can keep stale delegations warm.
The most powerful response to disrespect is not rage. Rage tells them they found the button. It is not a speech. Speeches tell them you still want approval. The most powerful response is a clean withdrawal. Less access. Less warmth. Less availability. No announcement. A new version of you they can no longer access.
@brankopetric00 Caching is to system architecture and DB design what photoediting tools are to photography. An attempt to compensate for poorly written code. Design for real-time experience.
AI models write code like a junior developer on Red Bull and 5 cups of coffee! Very fast and cocky confident, yet it needs a lot of code review. @AnthropicAI 's Claude 4 comes very close.
Trust, but verify autocompletion, always.
Laravel's implementation of the Inversion of Control (IoC) Principle makes switching to a different framework feel like asking for too much.
Dependency Injection is King!