Pry VS Pry Byebug

that's surprising considering `pry`[1] is such an amazing debugger IMO.

[1] https://github.com/pry/pry

All of my recent tutorials and projects were primarily managed using the default Ruby REPL, irb, and I must say it's been nothing short of amazing. However, what ultimately prompted me to switch to Pry was its offering of better defaults. But what exactly does that mean? Let me demonstrate:

For older versions: Pry Gem

To do that, I would install `pry` into your rails project and then use it look around right before your test fails.https://github.com/pry/pry

This means I can be editing a shell script and easily inject arbitrary regions into a shell buffer for immediate testing (point never leaves the window where I am editing, and I can view the shell output in an adjacent window). This is similar to what Robe does with Pry within an inferior Ruby process using comint.

https://pry.github.io/ - also a lot of features from Pry have made it into the default IRB these days, but I still use pry. I don't know the equivalent commands in IRB.

For debugging, while not multi-threaded, to my knowledge, is the pry gem for debugging. There are a few different flavors, for instance, my favorite is pry-byebug.

Github Link : https://github.com/pry/pry

For debugging, while not multi-threaded, to my knowledge, is the pry gem for debugging. There are a few different flavors, for instance, my favorite is pry-byebug.

For Ruby, Pry is popular and sometimes combined with pry-byebug for a more conventional stack navigation experience.

There is byebug integration for pry: https://github.com/deivid-rodriguez/pry-byebug