Live data from Hacker News

RoR Debugbar

debugbar.dev

31–40 of 80 posts

Re: RoR Debugbar

#31
post #18

Earlier quoted context omitted.

The downside is that if the project decides not to have that in the code, nobody gets it. Example: I suggest to a customer to use it. They decide they don't want it, I can't use it too.

That’s a good point, I didn’t consider it this way.

One thing to check out: ruby-lsp gets around this by using a custom gemfile, which enhances the project with the lsp's dependencies. That means you can use the gem, with bundler, without adding anything to the "official" project gemfile.

You could probably accomplish something similar, and possibly inject some rack middleware to add the view, or even mount it as a rails engine.

Re: RoR Debugbar

#34
post #16

Hi I’m the maker of the debugbar. If you have any feedback or question, just let me know. Thanks puuush for posting it.

Hey Julien, very nifty! Can you comment on the inspiration/ similarity with the Laravel Debugbar [1]? I noticed your GH says "Laravel by Night" :) [1] https://github.com/barryvdh/laravel-debugbar

I’m a big fan of the Laravel debugbar. I even added the Jobs collection when I started working on this https://github.com/barryvdh/laravel-debugbar/pull/1470

Re: RoR Debugbar

#35
post #15

Earlier quoted context omitted.

Last commit was 5 years ago. I feel like this is 80% of the rails ecosystem nowadays.

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.

Re: RoR Debugbar

#37

Earlier 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 isn't dead. In fact Hotwire and Stimulus have breathed some new life back into the community. With Rails 7 there's new and interesting changes happening like the normalize method for normalizing data before it's persisted to the database, the new testing coverage, and the new encrypted credentials, which can replace devise as it's easier to extend. STI is still awesome and concerns help DRY up the code. I know it's not the new kid on the block anymore, but if you code into a Rails way of doing things it's still crazy fast for rapid development.

Re: RoR Debugbar

#38

Earlier 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.

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

Re: RoR Debugbar

#39

Earlier 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

It’s a good choice for building a full stack web application. You know… the stuff that it is designed for.

Re: RoR Debugbar

#40

Earlier 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

Ruby is a very beautiful language both in logic and consistency. Rails is a mature framework. The ecosystem is very much alive albeit not “exciting” anymore and at the end of the day people use what they know. The 2010s have produced a large number of Rails developers. For the majority of CRUD apps Rails (or Laravel or Django) are just fine thus there’s no need to really make a switch. Finally, React can power a lot of things but in my experience it is far from offering the right integration and rapid development speed that something like Rails or Laravel come with.
Post reply on HN