I started using Pharo a year ago and its been a pleasure to work with. Great community.
I really like the Syntax comparison (slides 46-49).
And being able to serialize the debugging context of a running program to a file that can be stored for later
Unless you're used to the Smalltalk way, you'd never think serializing the debugging context of a running program would have any use at all.
I'd never had dreamed it'd be possible to do what I do regularly in my deployed web apps. When the error handler catches an error, it serializes the error and emails it to me in a fuel file. I can then fire up my _local_ Pharo environment, materialize the error, debug it with all its context, fix whatever code I need to and push the changes to my monticello repo.
Comments
I started using Pharo a year ago and its been a pleasure to work with. Great community.
I really like the Syntax comparison (slides 46-49). And being able to serialize the debugging context of a running program to a file that can be stored for later
Unless you're used to the Smalltalk way, you'd never think serializing the debugging context of a running program would have any use at all.
I'd never had dreamed it'd be possible to do what I do regularly in my deployed web apps. When the error handler catches an error, it serializes the error and emails it to me in a fuel file. I can then fire up my _local_ Pharo environment, materialize the error, debug it with all its context, fix whatever code I need to and push the changes to my monticello repo.
Wow thats really impressive . well done