Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggest pry > irb #11

Closed
caporta opened this issue Aug 17, 2015 · 4 comments
Closed

Suggest pry > irb #11

caporta opened this issue Aug 17, 2015 · 4 comments
Assignees

Comments

@caporta
Copy link

caporta commented Aug 17, 2015

In the boolean operators section of this module, we suggest they:

Drop into IRB and use !! (the "double-bang operator") to determine that the string "hi" is truthy:

Would it be better to suggest they "drop into pry" instead of IRB, since we already had students download and use it in the debugging with pry module?

@AnnJohn
Copy link
Contributor

AnnJohn commented Aug 19, 2015

@SophieDeBenedetto can you fix and/or close by 8/21

@SophieDeBenedetto
Copy link
Contributor

Hi, I'm closing this issue. Pry isn't a good fit here. Pry is good for freezing a ruby program while it runs to examine the inner workings. IRB is good for quick playground to explore ruby functionality.

@caporta
Copy link
Author

caporta commented Aug 19, 2015

So Pry's debugging facilities are actually only a portion of what it's capable of. It's also a fully functioning REPL (using the pry command), nearly identical to IRB just with added functionality. Here's a screenshot:

screen shot 2015-08-19 at 2 12 30 pm

Most devs would consider it a more powerful alternative to IRB. Definitely your call whether it's worth replacing IRB within the track curriculum, but it's definitely much more than just a debugger.

@SophieDeBenedetto
Copy link
Contributor

yea, I agree. I think we will leave as is for the time being though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants