Why does anyone think that multiple columns for a single story are a good idea on the web?
No need to be snarky. Just calmly state that you find the column layout to be difficult to read.
Show HN: pry-rescue — workflow-optimized debugging for ruby
11–20 of 31 posts
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#12Why does anyone think that multiple columns for a single story are a good idea on the web?
If you resize your browser to make it smaller it renders as one column.
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#13> Whenever an unhandled exception happens in your program, pry-rescue opens an interactive pry shell right at the point it was raised. Instead of glowering at a stack-trace spewed out by a dying process, you'll be engaging with your program as though it were still alive! The pry console gives you access to the method that raised the exception, you can use it to inspect the values of variables (no more print statement…
Same story as the Lisp folks. Good ideas need to be wrapped up in easy-to-understand, small packages for them to be picked up by the more mainstream languages.
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#14Why does anyone think that multiple columns for a single story are a good idea on the web?
Exclusively for you, my friend :)
Fix for Chrome (Stylebot): http://goo.gl/9qoeF
Fix for Firefox (Stylish): http://goo.gl/6tkpz
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#15For python, ipython --pdb does the trick. Don't forget to install ipdb too, much nicer than plain pdb.
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#16This is awesome work, thanks!
Just throwing this out there, I know a bit about the difficulties this would entail, but: Is it plausible to have something like this running in production mode?
I mean, if I had a production Rack app running and could have pry-rescue (somehow) save its state and bubble the exception up normally, and later connect to the process and inspect what went wrong. Would something like this be feasible?
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#17> Whenever an unhandled exception happens in your program, pry-rescue opens an interactive pry shell right at the point it was raised. Instead of glowering at a stack-trace spewed out by a dying process, you'll be engaging with your program as though it were still alive! The pry console gives you access to the method that raised the exception, you can use it to inspect the values of variables (no more print statement…
Ruby is pretty much an unholy mix of Perl + Smalltalk + a sprinkling of Lisp with an extreme syntactic sugar-bomb on top to start with. At least in terms of inspirations.
And I say that mostly as a compliment (though I still find the Ruby grammar atrocious from an implementation point of view).
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#18> Whenever an unhandled exception happens in your program, pry-rescue opens an interactive pry shell right at the point it was raised. Instead of glowering at a stack-trace spewed out by a dying process, you'll be engaging with your program as though it were still alive! The pry console gives you access to the method that raised the exception, you can use it to inspect the values of variables (no more print statement…
Ruby is pretty much an unholy mix of Perl + Smalltalk + a sprinkling of Lisp with an extreme syntactic sugar-bomb on top to start with. At least in terms of inspirations. And I say that mostly as a compliment (though I still find the Ruby grammar atrocious from an implementation point of view).
> And I say that mostly as a compliment (though I still find the Ruby grammar atrocious from an implementation point of view).
I think there is something deep embodied here. Syntactic sugar items for languages are like features for libraries. It's been said that if everyone is completely happy with a library's features, the library maintainers haven't been doing their job.
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#19This is awesome work, thanks! Just throwing this out there, I know a bit about the difficulties this would entail, but: Is it plausible to have something like this running in production mode? I mean, if I had a production Rack app running and could have pry-rescue (somehow) save its state and bubble the exception up normally, and later connect to the process and inspect what went wrong. Would something like this be f…
Yes :). I'm not exactly sure of the details, but I certainly want to try! See https://github.com/mrbrdo/rack-webconsole: there's already a rack-webconsole-pry, so it should be an easy step to hook it up to past exceptions.
Re: Show HN: pry-rescue — workflow-optimized debugging for ruby
#20is there any way to make this compatible with ruby 1.8.7? Seems like just what I need, but haven't upgraded my current app with a newer version of ruby.