Laravel VS turbo-laravel

It does not mean you should absolutely use it everywhere, but it can make sense for your case. Many frameworks, like Laravel use it to compose new projects.

https://github.com/laravel/framework/blob/00894b89e42a9d707c...

Even Tinker is a few lines of code to extend PsySH and credit is barely given.

Taylor Otwell is a fiend for creating wrappers around solid open source libraries, using PHP magic and encouraging bad practices, all just to breed an ecosystem ultimately to land him a Lambo, fuelled by amazing open source foundations that have barely been contributed back to by him.

This same system has been used in Laravel since version 4.0* albeit in the more PHP plain way, using call_user_func_array (Laravel Model Class).

laravel/framework: https://github.com/laravel/framework/pull/47309

And as far as what your title states “not optimized” the answer to this is yes, the code is not optimized. In some cases there are minor optimizations that are bizarre, and in other places, PRs for optimization are closed. It’s a bit arbitrary, but c’est la vie.

For instance, I've always learned to separate into methods when things become complicated/unreadable. Sometimes I see code that has something like this (excuse me on my phone, but Ive seen this a couple of times): https://github.com/laravel/framework/commit/8692f67960cb33a598d46dbed3fd12df15eb4a3f

The framework itself runs tests in public. You can see that the workflow with waiting for the machines takes around 6 minutes, but the run on a single platform e.g. PHP 8.2 - prefer-stable takes 2.5-3.5 minutes only. The tests themselves? Thousands in a minute:

We're also experimenting on a new project with Laravel + Hotwire (by using https://turbo-laravel.com/) and we're very, very excited about it. Seems to simplify a lot of things and so far checks all the boxes: all the security, robustness and features of laravel, SSR works by default, "SPA" like feeling, i18n works perfectly as its all default laravel stuff. So far it's working like a charm. Only drawback is that some (just one or two) React purists in our teams don't like it just because it is not hip.

Yes Turbo is created by the team behind Ruby on Rails and it's an evolution of Turbolinks with bunch of other functionality added. But Turbo can be adapted to other languages and backend frameworks (and already has!). This Turbo thing is not Rails specific.

Check out https://github.com/tonysm/turbo-laravel

Do you use it? How has your experience been? Did you use the package from https://github.com/tonysm/turbo-laravel? Any major gotchas or reason to avoid it?