Version 10.55.0 lost ~10.8 k rows of dev environment code that was moved to a separate package. https://marius-ciclistu.medium.c...

Version 10.56.0 brings faster boot time for apps that have many listeners for events and/or observers by improving the way they are registered, including caching the observers when events are cached. https://marius-ciclistu.medium.c...

Maravel-Framework 10.54.3, which is used in Maravel Micro-Framework and Maravelith Template, restricts the devCommands to local environment and by doing this, it speeds up the boot of the application. Also it contains a back-port for \Illuminate\Console\Prohibitable with the mention that these classes are by default prohibited from running in production:

• \Illuminate\Database\Console\Migrations\FreshCommand

• \Illuminate\Database\Console\Migrations\MigrateMakeCommand

• \Illuminate\Database\Console\WipeCommand

• \Illuminate\Database\Console\Migrations\ResetCommand

• \Illuminate\Database\Console\Migrations\RefreshCommand

• \Illuminate\Database\Console\Seeds\SeedCommand

The differences to Laravel/Lumen are:

Maravel 10.51.4 can process woth 15.965% more requests per second vs Lumen 10. This is without caching for config or routes and without opcache preload. More details https://github.com/myaaghubi/PHP...

Version 5.1.0 of laravel-crud-wizard-free will include a backward compatible (laravel >= 8) major performance improvement for reducing the number of set calls during updates when using casts. Also a new feature of locking the model to prevent updates will come as a bonus. Maravel-Framework 10.53.2 will also contain this improvement at a larger scale than the one possible via an external package. It will support prevention of updates also. More details .

Most people think users choose products based on features or price. In reality, support decides who stays.

A cheaper tool becomes expensive fast when every issue turns into a ticket nightmare. Meanwhile, teams keep paying more for products that solve problems and support them when it matters.

Support is not a cost. It is part of the product experience. Fast replies build trust. Clear answers reduce churn. Companies that treat support as a growth lever win.

I really wonder these questions

Most people think users choose products based on features or price. In reality, support decides who stays.

A cheaper tool becomes expensive fast when every issue turns into a ticket nightmare. Meanwhile, teams keep paying more for products that solve problems and support them when it matters.

Support is not a cost. It is part of the product experience. Fast replies build trust. Clear answers reduce churn. Companies that treat support as a growth lever win.

I really wonder these questions

Built for who needs more than Laravel can/wants to offer in terms of APIs.

This includes both new features and retroactive bug fixes.

If things like:

• auto incrementing via API

• auto filtering via API

• auto aggregating via API on the resource's & relations' columns

• auto streamed JSON Lines response

• auto CSV streamed download

• auto XLS download with relations in separate sheet (for current page)

• auto MVCC DB "select count(*) from table" slow query solution in MySql >= 8

• auto prevent DB blocking via API with long running queries for mysql >= 5.7.4 and mariaDB >= 10.1.1

• auto composite primary key handling

• read-only DTO for model

• auto update the one to one relations on resource update

• retroactive vulnerability fix for eager loading relations in global scopes

• and many more features that you can read about here: https://github.com/macropay-solu...

  seem unbelievable at first glance, be my guest and see for your self: https://laravel-crud-wizard.com