byebug vs pry-byebug

Overview

pry-byebug

Stacks353

Followers0

Votes0

GitHub Stars2.0K

Forks136

byebug

Stacks688

Followers0

Votes0

GitHub Stars3.3K

Forks334

pry-byebug vs byebug: What are the differences?

pry-byebug: Combine 'pry' with 'byebug'. Combine 'pry' with 'byebug'. Adds 'step', 'next', 'finish', 'continue' and 'break' commands to control execution; byebug: Byebug is a Ruby debugger. Byebug is a Ruby debugger. It's implemented using the TracePoint C API for execution control and the Debug Inspector C API for call stack navigation. The core component provides support that front-ends can build on. It provides breakpoint handling and bindings for stack frames among other things and it comes with an easy to use command line interface.

pry-byebug and byebug belong to "RubyGems Packages" category of the tech stack.

pry-byebug and byebug are both open source tools. It seems that byebug with 3.1K GitHub stars and 284 forks on GitHub has more adoption than pry-byebug with 1.77K GitHub stars and 118 GitHub forks.

September Test Company, Mashweb.Club, and **** are some of the popular companies that use byebug, whereas pry-byebug is used by 成都探码科技有限公司, ****, and ****. byebug has a broader approval, being mentioned in 52 company stacks & 15 developers stacks; compared to pry-byebug, which is listed in 34 company stacks and 8 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

pry-byebug	byebug
Combine 'pry' with 'byebug'. Adds 'step', 'next', 'finish', 'continue' and 'break' commands to control execution.	Byebug is a Ruby debugger. It's implemented using the TracePoint C API for execution control and the Debug Inspector C API for call stack navigation. The core component provides support that front-ends can build on. It provides breakpoint handling and bindings for stack frames among other things and it comes with an easy to use command line interface.
Statistics
GitHub Stars 2.0K	GitHub Stars 3.3K
GitHub Forks 136	GitHub Forks 334
Stacks 353	Stacks 688
Followers 0	Followers 0
Votes 0	Votes 0

What are some alternatives to pry-byebug, byebug?

rake

Rake is a Make-like program implemented in Ruby. Tasks and dependencies are specified in standard Ruby syntax. Rake has the following features: * Rakefiles (rake's version of Makefiles) are completely defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax to worry about (is that a tab or a space?) * Users can specify tasks with prerequisites. * Rake supports rule patterns to synthesize implicit tasks. * Flexible FileLists that act like arrays but know about manipulating file names and paths. * Supports parallel execution of tasks.

pry

An IRB alternative and runtime developer console.

rspec

BDD for Ruby.

rails

Ruby on Rails is a full-stack web framework optimized for programmer happiness and sustainable productivity. It encourages beautiful code by favoring convention over configuration.

simplecov

Code coverage for Ruby 1.9+ with a powerful configuration library and automatic merging of coverage across test suites.

puma

Puma is a simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Puma is intended for use in both development and production environments. It's great for highly concurrent Ruby implementations such as Rubinius and JRuby as well as as providing process worker support to support CRuby well.

pg

Pg is the Ruby interface to the {PostgreSQL RDBMS}[http://www.postgresql.org/]. It works with {PostgreSQL 9.2 and later}[http://www.postgresql.org/support/versioning/]. A small example usage: #!/usr/bin/env ruby require 'pg' # Output a table of current connections to the DB conn = PG.connect( dbname: 'sales' ) conn.exec( "SELECT * FROM pg_stat_activity" ) do |result| puts " PID | User | Query" result.each do |row| puts " %7d | %-16s | %s " % row.values_at('procpid', 'usename', 'current_query') end end.