Long running processes might die or get killed, one of the ways to monitor them is through heartbeats. Flow #PHP in next release will let you define frequency and hook into heartbeats.
That progression UI is a component built on top of Flow Pulse protocol
the most import skill in 2026 is still being able to tell your agents "wtf is this crap, no, not like this"
if you stop doing that, you're basically fucked, despite what some devfluencers would like you to think.
https://t.co/jXMPANwOFd - first results of @flowphp benchmarks against DuckDb 2.0 / Spark 4.0 / Polars 2.1
PHP is not the most spectacular, but it's not far behind other and in some places even beats them 💪
How about we first figure out the economy around token generators before we assassinate software development foundations?
At this moment, the situation resembles repairing the aircraft while it is airborne.
If you're a developer, pay attention to what Sam says below. 👇
Coding agents are changing local and global maxima.
In the extreme, frameworks & paradigms that were 'bad' before because 'boilerplate' / 'unfamiliar' can now dominate completely.
Unlearn what you have learned.
whats being removed is inefficient data format 😅 Just simply converting csv to parquet will give you that.
And if you by any chance work with #php you should check @flowphp which can convert 80mlns csv rows with schema inference into parquet in few seconds 😏
Those people wouldn’t be able to correctly identify php code if you show them the same thing written in Java, dotnet, ts and php.
The same people rarely understand how their language of choice works.
But yet they feel that they need to share their "precious" opinion online 🤷♂️
Seeing a lot of people seriously claim that if you're still using PHP in 2026 you deserve the vulnerability.
No real argument, just "it's old."
By that logic we should stop using C too.
They never consider that some ecosystems have been running for years for a reason.
or maybe (I know its crszy idea) all business running on php unsupported for over a decade migrate up and make migrations part of their software lifecycle?
Yea, software comes with lifecycle and maintenance.
There is literally no reason to help those businesses stay behind
Since we see the PHP fixes being back-ported by extremely helpful volunteers (and their agents) from 8.2, the oldest supported version, all the way to 5.x from 10 years ago, maybe now is the time to re-evaluate back-porting ALL security fixes with the help of AI system, right?
In 1994, software was dead. People told me programming was for nerds and that I should become a doctor or a lawyer instead.
In 2004, software was dead. People told me that someone from India would take my job for $5/hour.
In 2014, software was dead. People told me that no-code was going to kill every job and doom my career.
In 2024, software was dead with Devin, Windsurf, Copilot, and OpenAI o1.
We kill software every 10 years, and yet the demand for good Software Engineers has never been higher.
It is.
The US increasingly epitomises hyper-capitalist showmanship: a circus of clowns selling spectacle as innovation, with little added value to humanity.
Europe still has a sense of class: engineering with purpose, creating things people actually want, need and can use.
Spectacle vs substance
Tylko ktoś kto nigdy niczego nie utrzymywał, ani nie kierował zespołem ludzi, nie rozliczał się z bakclogu, nie miał klientów na karku może się ekscytować niekontrolowanym push streamem do repo
Wewnętrzne przyspieszenie w Anthropic, które zepchnęło ich infrastrukturę deweloperską do granic wytrzymałości.
AI tak mocno przyspiesza produkcję kodu (w tym własnego oprogramowania Anthropic), że firma musi przebudowywać fundamentalne narzędzia, żeby móc iść jeszcze szybciej. Claude był zarówno przyczyną problemu, jak i głównym narzędziem do zbudowania Sciona.
Publicznie pace the frontier, wewnętrznie wymieńmy gita, bo Claude generuje za szybko :)