3 ms·
In Smalltalk, you can start writing a debugger that lets you browse a stack trace in under 5 minutes. The debugger is just an ordinary application working on (
by stcredzero 16y ago
In Smalltalk, you can start writing a debugger that lets you browse a stack trace in under 5 minutes. The debugger is just an ordinary application working on (mostly) ordinary objects that happen to be the meta-level of Smalltalk. (In particular, the contexts.) To complete the debugger, you just need to implement a Smalltalk VM without GC, which is not all that hard, as it's little more than a 256 case switch statement. Basically, your debugger is a VM you control through an app, running the debugged process.
- mahmud 16y agoIn nearly every application domain, you can compare the Smalltalk way and the Other, and in nearly all the Smalltalk is better, but that doesn't mean people will listen. It's best to explicate your point using a 50-page tutorial on the Java Debugging API, Platform Introspection, and .NET Tracing Hooks, or whatever. Make it so hard that it's worth our time, then we will listen.
- tonyg 16y agoErm, your irony is a touch opaque. What do you really think?
- mahmud 16y agohttp://pharo-project.org/ http://pharo-project.org/ Download Pharo Smalltalk and fire it up. Download "Pharo by Example" ebook, from the same site, and open it up. I guarantee you this: with every page you read, you will grow to resent the cruft-peddling "mainstream" computing.
- tonyg 16y agoI see, and quite agree. As this is about to get off-topic, I'll follow this up with you separately :-)
- eliben 16y agoI fail to see how this is relevant. Smalltalk is a VM language, which makes things very different. For instance, I can say that for Python you easily write a debugger using the C API of the VM, and in fact you don't need to write a debugger, since one is part of the standard library. What point does this make?
- stcredzero 16y agoI fail to see how this is relevant. Sorry. Smalltalk is a VM language, which makes things very different Yet somehow, you have stumbled right on one of the major points. VM languages are often about eliminating impedance mismatch between ordinary coding and the metamagical stuff. Python is another good example, but I am less familiar with Python than Smalltalk. The same goes for Lisp and Ruby. I have written the "5-minute debugger" in Smalltalk as part of a presentation. (Really, it's just a stack browser.) I haven't done the same for the other languages.