ruby-lsp VS laravel-debugbar

Some details from https://github.com/Shopify/ruby-lsp

> NOTE: starting with v0.7.0, it is no longer recommended to add the ruby-lsp to the bundle. The gem will generate a custom bundle in .ruby-lsp/Gemfile which is used to identify the versions of dependencies that should be used for the application (e.g.: the correct RuboCop version).

After lunch, I parked at the Ruby LSP table. I worked with Julie and Drew on HEREDOC endings. We also found an issue that we spent some time digging into, but ran out of time before we had a solution. It was fun spelunking through the code with friends. Ufuk joined us in looking at the cursor indentation issue. His sage wisdom helped us navigate through an unfamiliar codebase.

Thanks for the feedback. Added an issue for you: https://github.com/Shopify/ruby-lsp/issues/594

Links: Ruby-lsp , vscode addon

Thanks. You might like to watch this RFC PR https://github.com/Shopify/ruby-lsp/pull/429 (from me) with the proof of concept implementation of indexing and a very simplistic go to definition implementation, which is now being productionized properly. The indexing logic has moved into Syntax Tree and now we have access to a uniform API in Ruby LSP.

Ruby LSP and its associated extension: https://github.com/Shopify/ruby-lsp

Laravel Debugbar: Laravel Debugbar is a package that integrates PHP Debug Bar with Laravel. It provides a convenient toolbar that sits at the bottom of your application's pages and offers insights into various aspects of your application, including database queries, route information, views, events, and more. With its customizable configuration options and extensive feature set, Laravel Debugbar is an excellent choice for monitoring database queries and debugging your Laravel applications.

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.