Thought this was going to be about debugging Rigs of Rods bars (joints). Meh
Thought this was about visualizing the 6502 rotate right instruction problem.
RoR Debugbar
51–60 of 80 posts
Re: RoR Debugbar
#52Earlier quoted context omitted.
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.
Yeah, right. Because all the interesting things nowadays happen on the same server that renders your html and nobody calls into other SaaS APIs or interacts with external systems much.
Rails is great for a world where an app was running on one server, but that world just isn't there anymore as much as it used to.
Re: RoR Debugbar
#53Earlier quoted context omitted.
How would you be able to implement this functionality only from the frontend without ever adding backend code? You'll always need to expose this info from the backend somehow. Of course with react and vue the data is available since it's already in the frontend.
Yeah you always need a backend part as part of your dev dependencies but currently you also need to add a little snippet in your production view code. It could be a browser extension like Rails panel + meta_request but I think it’s also good that anybody working on the codebase always get the debugbar, regardless of their browser or setup.
Couldn't you only have the snippet in the layout in dev environment? That's fairly common
Re: RoR Debugbar
#54First 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…
We recently installed something similar (https://miniprofiler.com) into a legacy ASP.NET MVC app. It is setup to only be visible in local development environments.
In areas of the code where ORMs obscure the actual SQL that runs, it's shortened the amount of time and effort it takes to discover a slow route and optimize it.
"Handy to have that extra info in your dev environment" is pretty spot on.
Re: RoR Debugbar
#55First 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…
We recently installed something similar ( https://miniprofiler.com ) into a legacy ASP.NET MVC app. It is setup to only be visible in local development environments. In areas of the code where ORMs obscure the actual SQL that runs, it's shortened the amount of time and effort it takes to discover a slow route and optimize it. "Handy to have that extra info in your dev environment" is pretty spot on.
[deleted]
Re: RoR Debugbar
#56Hey Julien!
Great to see that you finally released this ;)
Re: RoR Debugbar
#57Just curious... how come noone else in the ruby scene seems to use an actual debugger? IDEA has a front-end for ruby-debug-ide and it is divine, it puts pry to shame. Does VSCode or others not have this or something?
Some of the other stuff mentioned in the blog post... why tail development.log if you can tail stdout and get all that nice console coloration and such?
> I hate switching constantly between the browser, and the terminal where I tail the logs. I want to see the debugging information in the same window.
Get yourself multiple screens my dude.
That said, this looks like an interesting project.
Re: RoR Debugbar
#58After monitoring my portfolio performance, CASSANDRA_ E_ OAKLEY blew me away $70k in the last two quarters alone, I learned why these experienced traders make huge profits from the seemingly unknown market.. Also on Facebook CASSANDRA _E_ OAKLEY
Re: RoR Debugbar
#59Earlier quoted context omitted.
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 g…
Hey there, sorry if this came across as critique on the project itself or you personally. I get it, priorities change and projects get abandoned by the original maintainers.
My comment was more aiming at the ecosystem at large. Lots of the (RoR) stack in my current day job depends on long abandoned libraries with unmerged fix PRs from years ago and I see this all the time in the Rails ecosystem. Interest in the ecosystem is shrinking and this is one symptom.
Re: RoR Debugbar
#60Just curious... how come noone else in the ruby scene seems to use an actual debugger? IDEA has a front-end for ruby-debug-ide and it is divine, it puts pry to shame. Does VSCode or others not have this or something? Some of the other stuff mentioned in the blog post... why tail development.log if you can tail stdout and get all that nice console coloration and such? > I hate switching constantly between the browser,…
Most devs I've worked in across multiple languages don't use debuggers. They can't be bothered to spend a couple hours figuring it how to configure one. Meh, to each their own. I always spend the time configuring one and it always pays off.