News for hackers. Stuff that matters.
Re:Why Every Ruby Developer Should Learn Smalltalk by cwp on Tuesday April 17, 2012 @04:38PM (#3854872)
Even better is the interaction between the test runner and the debugger. Unit tests are orders of magnitude more useful when you can just open a debugger on a failing assertion.
Re:Why Every Ruby Developer Should Learn Smalltalk by stcredzero on Tuesday April 17, 2012 @04:49PM (#3854920)
And just as good: when you refactor your code, the same refactoring is often automatically applied to your tests.

And the web frameworks: in many of them, you can just debug the rendering of the web page.

Re:Why Every Ruby Developer Should Learn Smalltalk by igrekel on Tuesday April 17, 2012 @05:58PM (#3855245)
Not to mention the integration between the debugger and Seaside... I always get a few jaw drops when I fix code and the page comes up once I press "Proceed".
Re:Why Every Ruby Developer Should Learn Smalltalk by stcredzero on Tuesday April 17, 2012 @08:41PM (#3855800)
The thing is, that's not really "integration." That's just the Debugger doing what it usually does. There's no abstruse code supporting that. (Usually Smalltalk environment "integration" does require a few lines of pedestrian code.)
Re:Why Every Ruby Developer Should Learn Smalltalk by cwp on Tuesday April 17, 2012 @09:47PM (#3856057)
Well, Seaside does have explicit code to support the debug link. If you get an exception during rendering, the framework generates a 500 response with a "Debug" link. Clicking the link restarts the previous request, and when it hits the exception, it opens a debugger instead of generating the 500 response. If you fix the error and continue, the page is sent to the browser as usual.

It's not a lot of code, but it's pretty clever.

Re:Why Every Ruby Developer Should Learn Smalltalk by lucian1900 on Tuesday April 17, 2012 @05:03PM (#3854979)
py.test --pdb has this exact feature and I love it. Now I almost exclusively debug with unit tests.
Re:Why Every Ruby Developer Should Learn Smalltalk by kingkilr on Tuesday April 17, 2012 @09:50PM (#3856062)
I was going to say, is that not a standard feature of test runners today? py.test is amazing though :)