ruby-debug included in stdlib in 3.1 (!!)

Hello !

I've been a big fan of byebug for many years and it's a major piece of my
workflow.

Well, looks like in 3.1, the gem ruby-debug will be included in the stdlib.
This would be a big change for me ! I'm looking forward to learning more.

On the one hand, "if it ain't broke ..." --> *but*,

* this *is* one less gem to install, and added simplicity is a plus in my
book
* maybe there's something more to learn with the new gem for better
debugging
* the Ruby core devs are super smart and must have good analysis here .

Anyhow, when I saw this on the /r/rails subreddit it was a big deal to me !

···

--
A musician must make music, an artist must paint, a poet must write, if he
is to be ultimately at peace with himself.
- Abraham Maslow

Yes, it does look like a big deal :slight_smile: I'm looking forward to trying out
some of the new features; debug over TCP socket, break on specific
exceptions, and maybe editor integration.

San Lo, (a contributor) posted this sneak peek a little while back

-gf-

···

On Wed, Sep 29, 2021 at 12:52 PM Sean Felipe Wolfe <ether.joe@gmail.com> wrote:

Hello !

I've been a big fan of byebug for many years and it's a major piece of my
workflow.

Well, looks like in 3.1, the gem ruby-debug will be included in the
stdlib. This would be a big change for me ! I'm looking forward to
learning more.

https://www.reddit.com/r/rails/comments/pxrfy7/rails_7_replaced_byebug_with_rubydebug/
Rails 7 replaced byebug with ruby/debug | Saeloun Blog

On the one hand, "if it ain't broke ..." --> *but*,

* this *is* one less gem to install, and added simplicity is a plus in my
book
* maybe there's something more to learn with the new gem for better
debugging
* the Ruby core devs are super smart and must have good analysis here .

Anyhow, when I saw this on the /r/rails subreddit it was a big deal to me !

--
A musician must make music, an artist must paint, a poet must write, if he
is to be ultimately at peace with himself.
- Abraham Maslow

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<ruby-talk list: member options login page>

Indeed a big deal. On the surface, it might look like it's very similar to
byebug, but being integrated with ruby makes it avoid the main issues of
using byebug:

* support for multithread (and ractor) debugging
* resilience towards redefining classes (byebug doesn't play well with the
"zeitwerk" autoloader).
* editor / container debugging.

Being a tool from ruby core has also better guarantees of stability
whenever new ruby versions come out the door.

Gerard Fowley <gerard.fowley@iqeo.net> escreveu no dia quarta, 29/09/2021
à(s) 22:42:

···

Yes, it does look like a big deal :slight_smile: I'm looking forward to trying out
some of the new features; debug over TCP socket, break on specific
exceptions, and maybe editor integration.

San Lo, (a contributor) posted this sneak peek a little while back

A Sneak Peek of Ruby's New Debugger! - DEV Community

-gf-

On Wed, Sep 29, 2021 at 12:52 PM Sean Felipe Wolfe <ether.joe@gmail.com> > wrote:

Hello !

I've been a big fan of byebug for many years and it's a major piece of my
workflow.

Well, looks like in 3.1, the gem ruby-debug will be included in the
stdlib. This would be a big change for me ! I'm looking forward to
learning more.

https://www.reddit.com/r/rails/comments/pxrfy7/rails_7_replaced_byebug_with_rubydebug/
Rails 7 replaced byebug with ruby/debug | Saeloun Blog

On the one hand, "if it ain't broke ..." --> *but*,

* this *is* one less gem to install, and added simplicity is a plus in my
book
* maybe there's something more to learn with the new gem for better
debugging
* the Ruby core devs are super smart and must have good analysis here .

Anyhow, when I saw this on the /r/rails subreddit it was a big deal to me
!

--
A musician must make music, an artist must paint, a poet must write, if
he is to be ultimately at peace with himself.
- Abraham Maslow

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<ruby-talk list: member options login page>

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<ruby-talk list: member options login page>