my first project

hey guys! This is my first PHP project. It’s a website designed to practice reading code in different programming languages, where a new daily challenge appears in a random language every day (inspired by games like Wordle).

If anyone is interested in trying it out: https://dailycode.page.gd

I also made the project’s source code available on GitHub: https://github.com/rafssunny/dailycode

https://redd.it/1qwj01p
@r_php

Taylor just DM'd the guy who made Adonisjs 👀
https://redd.it/1qwjqcq
@r_php

New in LarAgent: Automatic Provider Failover and Smarter Tool Development
https://blog.laragent.ai/new-in-laragent-automatic-provider-failover-and-smarter-tool-development/

https://redd.it/1qwltf4
@r_php

Expression Parser in PHP/JS for form validation – feedback welcome

I built an expression parser used for form validation and calculated fields, with the same logic implemented in both PHP and JavaScript.

To test it properly, I set up two separate pages: one running the parser in JavaScript, one running the same expressions in PHP.

I’d really appreciate some help testing it:

Are there any inconsistencies or bugs between the PHP and JS versions?
Do you think any fundamental operators or functions are missing?

JS version: https://milkadmin.org/milk-admin/?page=expression-parser
PHP version: https://milkadmin.org/milk-admin/?page=expression-parser&action=php

For anyone interested in how the PHP version was built, I also wrote an article explaining the core steps involved in developing a mathematical expression parser:
– Splitting the input into tokens
– Building an Abstract Syntax Tree (AST)
– Recursively evaluating the AST

The article focuses on algorithms and data structures, not on any language-specific feature or library.

Article: https://www.milkadmin.org/article.php?id=07-ast

It’s meant as an introduction for those who enjoy understanding how things work under the hood.



https://redd.it/1qvtprr
@r_php

Are you using Leaf PHP?

While I like Laravel, I feel it's just too bloated for every project. I started using Leaf PHP, love it! clean API, lean and you can bring in Laravel stuff when needed.

Compared to the big two Laravel and Symfony, there's not much mention of other PHP frameworks.

Are you using Leaf? and can you describe the nature of your app. e.g. "Hobby", "Commercial with 10k users" etc...

Feel free to elaborate on why you prefer leaf and any other thoughts you may have on it.

Thanks!

https://redd.it/1qwouxa
@r_php

Laravel AI SDK just dropped
https://laravel.com/docs/12.x/ai-sdk

https://redd.it/1qwqgxe
@r_php

Preparing for the job

Hello!

In three weeks I start with my first fulltime job as a backend PHP dev. I have some experience with Symfony at an internship/summer job. But to prepare for the job ahead I want to take these weeks to get some hands on experience again with PHP/Symfony.

I was thinking of creating a cool useful composer package from which I can learn a lot! Maybe something that Symfony/PHP/Composer is now missing. Anyone got cool ideas? Or any other ideas on how I can prepare myself for the job ahead? Maybe cool projects?

Thanks in advance!

https://redd.it/1qwrafh
@r_php

Building with the New Laravel AI SDK w/ Taylor Otwell
https://www.youtube.com/watch?v=8MJ7r6niTus

https://redd.it/1qwrvwl
@r_php

Laravel 12.49: New Collection Method, Query Builder Upgrade & Better Artisan
https://youtu.be/3iL51liqYiw

https://redd.it/1qwwldl
@r_php

Symfony Components Tutorial

Is there any good tutorial about using Symfony Components in a PHP Project without necessarily using the entire Symfony Framework? Better still, on creating a framework from scratch out of Symfony components. Thanks.

https://redd.it/1qx2zyv
@r_php

Oracle - Passing null to parameter #X of type string is deprecated

I'm not a fan of not being able to pass nulls to some functions that expect strings, for example, trim(). I think being able to pass nulls to trim() would be a helpful language feature.

One specific example: Oracle treats empty strings as null. So, when I get a row from the database, the fields that I set to empty strings will be in the row array I get back. In the future, if I called strpos() on this null field, it will be a fatal error. I believe this only serves to make things more difficult and does not prevent any other errors.

Another example: a form where different users see different fields, but whatever text they type in will be run through trim(). A null is as good as an empty string to me in that case.


Is this a fair argument? Why or why not? I'm trying to understand the philosophy behind this language decision.

https://redd.it/1qx4m91
@r_php

Laravel has released the official AI SDK after long anticipation
https://jpcaparas.medium.com/130b8c84367f?sk=684eb43657d18f2bbb192038dfc6d664

https://redd.it/1qx2lec
@r_php

Does Laravel AI SDK possess agent orchestration facilities?

I am reading the documentation and can't see anything along these lines.

https://redd.it/1qxfnv4
@r_php

Memory For Laravel AI SDK
https://github.com/eznix86/laravel-ai-memory

https://redd.it/1qxg0sh
@r_php

Laravel AI SDK Full Review: Agents, Images, Audio, Tools & More
https://youtu.be/pE2yA25grGo?si=VriWBE2x81HWzbX9

https://redd.it/1qxhmgn
@r_php

Laravel NestedSet: Query tree structures efficiently

Hi r/php

We are proud to announce the availability of the aimeos/laravel-nestedset package, an improved version of the most popular Laravel/PHP package ([kalnoy/](https://packagist.org/packages/kalnoy/)nestedset) using nested sets for managing trees which, unfortunately, have been virtually abandoned by its owner.

Repo: [https://github.com/aimeos/laravel-nestedset](https://github.com/aimeos/laravel-nestedset)

The 1.0 release contains:

* Bugfix PRs from the original repo
* Support for UUID and custom ID types
* Full support for SQL Server
* PHPUnit 11/12 support
* Improved documentation

There's now a web site available for the documentation too:

[https://laravel-nestedset.org](https://laravel-nestedset.org)

We will continue supporting the package and if you like it, leave a star :-)


https://redd.it/1qxiwpg
@r_php

Version 13 of PHPUnit is released
https://phpunit.de/announcements/phpunit-13.html

https://redd.it/1qxli6j
@r_php

Upgrade to PHPUnit 12.5 in 7 Diffs
https://getrector.com/blog/upgrade-to-phpunit-125-in-7-diffs

https://redd.it/1qxma5o
@r_php

Real-world examples of using Laravel AI SDK
https://amitmerchant.com/real-world-exmples-using-laravel-api-sdk/

https://redd.it/1qybmk5
@r_php

Is Openswoole in maintenance mode and it's better to use regular Swoole?

As far as I can tell, openswoole's last commit to github was just adding php 8.4 support last year. Meanwhile swoole/swoole-src seems very actively developed. Which is strange considering in this sub I've always found people saying openswoole is more actively developed and it's future seems brighter than regular swoole.

https://redd.it/1qxpibx
@r_php

In 2026, what's the best way to handle building assets for deployment?

For the longest time I always ran npm ci && npm run build as part of the deployment noscript (via Forge, Ploi etc) but I would end up with deployments taking anywhere from 35-50 seconds, most of it being due to the asset building and I got really tired of it.

Earlier today I took out public/build from the .gitignore, committed the public/buildassets and setup a GitHub actions workflow that would build the assets for me. I'm indecisive if I like the idea of committing "dynamic" files to a repository. Addititionally I'm concerned about forgetting about asset compilation, building them locally and running into weird git merge conflicts. (although I'm not sure if this is a legitimate issue, and merge conflicts terrifiy me most of the time anyway)

I tend to make lots of mini deployments so taking the app down for 30-45 seconds multiple times a day feels really bad.

For those in similar shoes, what do you typically do?

https://redd.it/1qyq82y
@r_php