turbo-laravel VS laravel-debugbar

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?

debugbar And n+1 query

tldr using debugbar is a good point, everything else is just use laravel when using laravel and avoid n+1 problem

Nice but I can get the same functionality with the debugbar - what makes this better?

We then used platform-specific performance analysis tools to determine which of these endpoints needed the most attention. The highest-traffic sites we needed to optimize used Laravel, a popular PHP framework. We used Laravel Debugbar to analyze those web apps.

Try installing laravel-debugbar, it will show you which parts of the app are slow (e.g. boot up vs views), which queries are slow, and how many queries run (helpful when you forgot to eager load some models).

I wanted to tweak Laravel Debugbar, so it could also work with any JSON API, but I ended up writing a minimal package of my own to do the trick.