This seems pretty similar to https://github.com/dejan/rails_panel. Was that your inspiration?
RoR Debugbar
41–50 of 80 posts
Re: RoR Debugbar
#42Earlier quoted context omitted.
I definitely get that feeling as well. 80% ghost town
I'm moving from Phoenix back to Rails for a new project. Is it true Rails is dead? I thought it's community was at least 10x the size of Elixir's.
Rails is practically unusable for anything that requires concurrency inside of serving one request. If you have all your data in the database that your rails app connects to everything is great. If you need to call out over the network to 12 different services to serve your request or want to do computationally intensive things, etc, another language with support for concurrency is a better choice imho.
Re: RoR Debugbar
#43Earlier quoted context omitted.
There's peek[1], albeit not exactly the same thing [1] - https://github.com/peek/peek
Last commit was 5 years ago. I feel like this is 80% of the rails ecosystem nowadays.
I don't think this is quite right. I've done a survey a few months ago when deciding what to use for a new project (primarily comparing Ruby and Go). What I saw was many people rallying around the top useful libs out there. I also saw numerous brand new libs showing up, fixing mistakes of their predecessors. And each time I compared a popular Ruby project with a popular Go one, I'd find consistent activity from multiple maintainers in the former. And a lot of initial activity that completely dies down in the latter.
The overall feeling I got is that Ruby on Rails has gotten a lot more "getting shit done", "don't waste time" mode, — many businesses depend on it. Libs became higher quality compared to the early playful years.
Re: RoR Debugbar
#44Earlier quoted context omitted.
I'm moving from Phoenix back to Rails for a new project. Is it true Rails is dead? I thought it's community was at least 10x the size of Elixir's.
I dont know People who use Rails really seem to love it. But in 2024 things like react and typescript exists. Python is there for data science stuff Typescript is there for the web. I don't understand why you would pick Ruby instead
> react and typescript
These are nonstarters for me. It seems like vercel has corrupted react beyond recognition, and other full-stack frameworks like Remix just do a lot of `rigamarole` to mimic a fraction of what an older fullstack framework like rails/django/phoenix can do.
frontend is desperately trying to catch up to backend.
backend is trying to capture frontend to seduce people back, and they're getting there with freakishly good UX like phoenix liveview and rails 8's morph.
Re: RoR Debugbar
#45First time encountering the term 'debugbar', I see:
> This project is inspired by what you get in the PHP world, with the Laravel debugbar for instance.
Curious to know what a debugbar does? From a read of the docs (and a play around) it looks like it lets you navigate your site as usual, but it displays which controller/action got you to the page, any callbacks, and database queries. Anything else? What's a typical use case for this, or is it more like turn it on and it's just handy to have that extra info in your dev environment?
Re: RoR Debugbar
#46Earlier quoted context omitted.
I'm moving from Phoenix back to Rails for a new project. Is it true Rails is dead? I thought it's community was at least 10x the size of Elixir's.
I dont know People who use Rails really seem to love it. But in 2024 things like react and typescript exists. Python is there for data science stuff Typescript is there for the web. I don't understand why you would pick Ruby instead
> But in 2024 things like react and typescript exists.
Avoiding this stuff is one point on the list. I know I'm being a little snarky, but it's true. If you're building a fullstack app with fullstack devs you can avoid a lot of complexity that stuff brings.
Re: RoR Debugbar
#47First time encountering the term 'debugbar', I see: > This project is inspired by what you get in the PHP world, with the Laravel debugbar for instance. Curious to know what a debugbar does? From a read of the docs (and a play around) it looks like it lets you navigate your site as usual, but it displays which controller/action got you to the page, any callbacks, and database queries. Anything else? What's a typical…
It's for having in your dev environment and/or sometimes as a toggle for "Special Requests" -- if your session is authenticated and you're marked as blessed, you get extra information about what the application is doing under the hood so you can see what's going on in production as well.
Some let you add whatever information you want into the panel.
It's a convenience feature to make it easier to wade through information rather than having to dredge everything out of logs by hand, which a lot of people still do.
Re: RoR Debugbar
#48Earlier quoted context omitted.
I'm moving from Phoenix back to Rails for a new project. Is it true Rails is dead? I thought it's community was at least 10x the size of Elixir's.
Rails is practically unusable for anything that requires concurrency inside of serving one request. If you have all your data in the database that your rails app connects to everything is great. If you need to call out over the network to 12 different services to serve your request or want to do computationally intensive things, etc, another language with support for concurrency is a better choice imho.
You could say the same for PHP. But for 99.9% of applications, that doesn't apply.
Re: RoR Debugbar
#49This seems pretty similar to https://github.com/dejan/rails_panel . Was that your inspiration?
Laravel's debugbar is the inspiration.
Re: RoR Debugbar
#50Earlier quoted context omitted.
There's peek[1], albeit not exactly the same thing [1] - https://github.com/peek/peek
Last commit was 5 years ago. I feel like this is 80% of the rails ecosystem nowadays.
Author of peek here. Honestly, I got burnt out. We stopped using this internally at GitHub for our secondary Rails applications which made it difficult to continue working on. Rails was going through its identity crisis with asset pipelines and I didn't feel like trying to support every available option for people like Sprockets, Importmaps, NPM, Bower, etc. It was nice when there was the paved path and users could generally follow the README and be up and running quickly.
https://github.com/MiniProfiler/rack-mini-profiler gets you most of the way there and comes by default in the Gemfile for new Rails applications.