appsignal vs byebug

Overview

byebug

Stacks688

Followers0

Votes0

GitHub Stars3.3K

Forks334

appsignal

Stacks7

Followers0

Votes0

GitHub Stars162

Forks105

🔥 Trending in Languages on StackShare

JavaScript Languages

Lightweight, interpreted, object-oriented language with first-class functions

Try it View Docs Alternatives

Try

499

284k

Detailed Comparison

byebug	appsignal
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.	The official appsignal.com gem.
Statistics
GitHub Stars 3.3K	GitHub Stars 162
GitHub Forks 334	GitHub Forks 105
Stacks 688	Stacks 7
Followers 0	Followers 0
Votes 0	Votes 0

What are some alternatives to byebug, appsignal?

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.