Pry VS appmap-ruby

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.

AppMap currently supports Ruby, Java, Python, and Javascript projects and the libraries are MIT licensed.

Yes, sure. I've added a link to the docs above, and the repo is here - https://github.com/applandinc/appmap-ruby

Well, I’m definitely biased, but we welcome devs at all XP levels at the appmap project. Take a look. If you can’t find a good first issue @ Dan, Dustin, Kevin, or Petr in the Discord and someone will hook you up. https://github.com/applandinc/appmap-ruby We have needs from doc to core features!

In order to help make this a reality, we have created the open source AppLand Framework. The AppLand Framework includes components to:

AppLand is an open source framework that developers can use to record, analyze, and optimize end-to-end code and data flows. The framework provides client agents for Ruby, Java and Python (beta) that record running code and generate JSON files called AppMaps. Users can view and analyze AppMaps locally using the AppMap extension for VS Code, and also push AppMaps to the AppLand server for analytics, sharing, discussion etc.

Now, what if you want to be able to efficiently fetch a subset of JSONB data, without having to load and parse every object? At AppLand, we store AppMap data in the database. Each AppMap has a mandatory section called metadata, and we want to be able to efficiently pull out the metadata of selected rows without having to parse the entire JSONB column (the metadata is usually less than 1% of the total JSON object). Awesomely, since PostgreSQL 12, PostgreSQL has a feature called generated columns.

Install the appmap gem by following the instructions in the README. Here's a quick checklist:

[3] AppLand framework, a tool to record, display, and analyze end-to-end code and data flows.