Benoit Jacquemont

To speed up debugging, a analyzer could try to find the heaviest objects (including it's children), or the heaviest tree path in the objects dependency graph.

Registered callables like autoloader or error handler not taken into account

1

These callables could be Closure, hence objects that take some space in memory.

This kind of tools would be cool: https://github.com/anvaka/pm

In objects list, display a configured property of the object

3

In a lot of cases, providing the object list with only the class name is not sufficient. Identifying a specific instance could be needed. Even if there's no standard object...

Updates the documentation about 4.0

2

- Flysystem (local, minio, distant) - HTTPS behind a proxy - cluster good practices (memcache for ACL, sharing media with object storage) - versioning purge in crontab